Page 3 of 20

Posted: Tue Aug 08, 2006 8:12 am
by Zapper
ShadowFoxx wrote:QUOTE (ShadowFoxx @ Aug 7 2006, 07:39 PM) if anyone is willing to take the time to teach... I'd totally be down with helping.
There are a lot of Video tutorials about using a paintprogram on the web and there are several tool's to make the work easy.... I will not teach you but i can give constructive critisism on your marterial.
If your have the urge to work with pictures, dig in and start with the tutorials, its not rocket science or make or break.
Its fun hard work and patience, learn to go for the picture in your mind and focus on the feeling u have associated with that picture.

Enjoy
Zap

Posted: Tue Aug 08, 2006 3:14 pm
by Zapper
Your_Persona wrote:QUOTE (Your_Persona @ Aug 8 2006, 01:38 AM) allegiance with high rez patch
Is it necessary to overwrite the the server files?? The UI stall's when it trys to contacts the allegiance game server!!

Posted: Tue Aug 08, 2006 10:16 pm
by pedro0930
Zapper wrote:QUOTE (Zapper @ Aug 8 2006, 08:14 AM) Is it necessary to overwrite the the server files?? The UI stall's when it trys to contacts the allegiance game server!!
yeah, how do you install the patch?
ASGS can't varify it's version so I can only play in training mission.
I don't really notice anything different :(

Posted: Wed Aug 09, 2006 1:41 am
by Your_Persona
Zapper wrote:QUOTE (Zapper @ Aug 8 2006, 09:14 AM) Is it necessary to overwrite the the server files?? The UI stall's when it trys to contacts the allegiance game server!!
Can you do any testing in the training mission? I'll try to get a new server that works /doh.gif" style="vertical-align:middle" emoid=":doh:" border="0" alt="doh.gif" />

QUOTE yeah, how do you install the patch?
ASGS can't varify it's version so I can only play in training mission.
I don't really notice anything different :([/quote]

You wont be able to play online with this version, its for local testing only. Test in the training missions, or with a lan server (when it works).
There is an option in the esc menu to enable the hirez textures, though you wont notice any difference unless you have put some high rez textures in your artwork folder.

Posted: Wed Aug 09, 2006 7:41 am
by Your_Persona
Ok I rebuilt it again.

This server should work for you. This is only for testing the hirez client. It will only run from using allsrvUI.

http://austin.bluedepot.com/alleg/allegiance(hirezTEST).zip

Again, if your not testing high resoultion textures you should ignore this.

you will want to backup your current allegiance.exe and any files you are overwriting with these ones.

Run allsrvUI.exe to start your server, create a game, then you can connect to it using the allegiance.exe in the zip.

Hope this works for you.

Posted: Wed Aug 09, 2006 2:07 pm
by Zapper
I got it runnig... i had to remove the service in order to get to run.

Posted: Wed Aug 09, 2006 4:46 pm
by Zapper
Its running ok... but i cant get alleg to load the models with the new tex.
It still load the 254 tex on the models...
I replaced the Old tex with the new hirez in the artwork folder.... Do i need to remap the tex in a modler.
I thougth that alleg would take the texs from the artwork folder the xxx.bmp.mdl and wrap the Models...
In MDLview i can see the model with the tex i replace..

My config:

I run the Hirez alleg for the Freealleg folder and place my tex in the subfolder artwork!

---Freealleg
|----artwork

The server is running in its own folder

---Alleg
|---server

Zap

Posted: Wed Aug 09, 2006 10:21 pm
by Zapper
I found the problem...

In the Reg there are 2 subbranches to Allegiance 1.0 and 1.1
In both branches the artpath is pointing to the normal Alleg folder. so i added Free to the 1.1 branch and i got my textures....
Now i just need to replace my testtexture(ugly purple squares) with the real high res tex's.

There is one thing that i don't get.... The Release FAZ2 is a version 1.1 and yet it use the 1.0 branch in Reg.
First i would say I'm glad, and second i think its sloppy(maybe a harsh word).
Are we protecting the Beta release enviroment in the registry by keeping the "Old" branch so the Beta can use the 1.1 branch??
Or is there another reason, like we are using windows so we/It tell the diff any way /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

Posted: Wed Aug 09, 2006 11:57 pm
by Tigereye
We use the two keys to keep the beta environment different from the production environment.

Regular Allegiance uses the 1.0 keys, and if you are using a beta client it will use the 1.1 keys. In this way you can safely run a beta client on the machine even if there is a regular installation without fear of accidentally breaking or modifying your regular installation.

I guess when we released R2 it wasn't really necessary to force everyone to start using 1.1 keys, and make a brand new key 1.2 or whatever. Plus, since we denote our releases by release number, it's not really a classic "version number" that is increasing.

There may be 10 releases over the next few years, and that definitely won't be a 2.0 release, so unnecessarily incrementing the version# will become problematic.

Either way: it doesn't hurt, it only helps. /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

--TE

Posted: Thu Aug 10, 2006 6:28 am
by Draco429
Hey, all. First post here on the Allegiance boards. I'm from the XWAU forums. I'm assuming it was Raveen that brought me over... he's Ol over there.

I'm not one of their prodigies by any means, but I know my way around Photoshop and know how to touch things up. I'm pretty sure I've found the textures that need to be updated... but I don't know what they look like when they've been mapped. Can anyone post some pics of a specific ship or whatever they'd like done?