Texture Colors and Crash

RealPandemonium · Post by **RealPandemonium** » Wed Nov 18, 2009 8:45 pm

-------------------------------------------------------------------------------------------------------------------
Windows Version (and Service Packs): Vista Home Premium
Processor Speed: 2 GHz
RAM: 2 GB
Video Card (Make and Model#): Mobile Intel 945 Express Chipset Family

After updating to R5, many textures including some ship and base textures are colored blue-black, very dark so that it is difficult to see them. Sometimes they are completely black, like silhouettes. This is especially agitating in a turret, where the red targeting arrow is now black and meshes with the background.

Additionally, I just experienced a crash right as we killed a miner. The moment the miner was about to explode, Allegiance crashed to desktop with no error message.

Screenshots will be taken by the end of the day so that you can see the color issue.

Thanks for reading.

*Update: The color problem seems to disappear after a while, but it returns when I select my loadout.

Here is a screenshot. I couldn't get any out of base shots because by this point it was only occurring in the loadout screen.

http://i50.tinypic.com/2ih9ta1.jpg

ogorass · Post by **ogorass** » Fri Nov 20, 2009 1:09 pm

Could you please post the contents of VideoSettings.log, DeviceCreation.log and DirectInput.log files found in your Allegiance folder?

RealPandemonium · Post by **RealPandemonium** » Fri Nov 20, 2009 8:21 pm

VideoSettings.log
-------------------------------------------------
Log file VideoSettings.log created - Nov 19, 19:40

Created D3D9 interface.
Found 1 adapters.
Extracting adapter 0: \\.\DISPLAY1 - Mobile Intel® 945 Express Chipset Family
800 x 600 @ 60Hz [32 bit] [HW 1 WND 1 DS 77 AA 0x01]
1024 x 768 @ 60Hz [32 bit] [HW 1 WND 1 DS 77 AA 0x01]
1280 x 600 @ 60Hz [32 bit] [HW 1 WND 1 DS 77 AA 0x01]
1280 x 720 @ 60Hz [32 bit] [HW 1 WND 1 DS 77 AA 0x01]
1280 x 768 @ 60Hz [32 bit] [HW 1 WND 1 DS 77 AA 0x01]
1280 x 800 @ 60Hz [32 bit] [HW 1 WND 1 DS 77 AA 0x01]
800 x 600 @ 60Hz [16 bit] [HW 1 WND 1 DS 77 AA 0x01]
1024 x 768 @ 60Hz [16 bit] [HW 1 WND 1 DS 77 AA 0x01]
1280 x 600 @ 60Hz [16 bit] [HW 1 WND 1 DS 77 AA 0x01]
1280 x 720 @ 60Hz [16 bit] [HW 1 WND 1 DS 77 AA 0x01]
1280 x 768 @ 60Hz [16 bit] [HW 1 WND 1 DS 77 AA 0x01]
1280 x 800 @ 60Hz [16 bit] [HW 1 WND 1 DS 77 AA 0x01]

FOUND RESOLUTIONS (MODE 0) (MAXRATE: 60):
0) 800x600 @ 60
1) 1024x768 @ 60
2) 1280x600 @ 60
3) 1280x720 @ 60
4) 1280x768 @ 60
5) 1280x800 @ 60
CURRENT IN-GAME RESOLUTION: 1024x768 @ 60

User selected values:
AD 0 MON 0x00010001 WIN 0 VSYNC 0
Fullscreen settings:
FMT 22 W 800 H 600 RR 60 DEP 77
Windowed settings:
FMT 22 W 800 H 600 RR 60 DEP 77
FSMS 0 WINMS 0
MIN 7 MAG 7 MIP 2
Window offset: 0 0

Log closed.

DeviceCreation.log
--------------------------------------------------
Log file DeviceCreation.log created - Nov 19, 19:40

CD3DDevice9 initialised.
Direct3DCreate9 succeeded.
Pure HWVP device creation failed: 0x8876086c.
HWVP device creation failed: 0x8876086c.
SWVP device created.
Device supports A1R5G5B5 format.
Device creation finished.

Log closed.
-------------------------------------

DirectInput.log
------------------------------------
Log file DirectInput.log created - Nov 19, 19:40

Initialized DirectInput
StaticEnumDeviceCallback:
pdidi->dwDevType: 12 (subtype: 1)
pdidi->tszProductName: Mouse
Initialized mouse stream - Axes: 3, Buttons: 5, POVs: 0
StaticEnumObjectsCallback:
pddoi->guidType: {A36D02E0-C9F3-11CF-BFC7-444553540000}
pddoi->tszName: X-axis
pddoi->dwType: 1 (instance: 0)
pddoi->wUsage: 0 (page: 0)
StaticEnumObjectsCallback:
pddoi->guidType: {A36D02E1-C9F3-11CF-BFC7-444553540000}
pddoi->tszName: Y-axis
pddoi->dwType: 1 (instance: 1)
pddoi->wUsage: 0 (page: 0)
StaticEnumObjectsCallback:
pddoi->guidType: {A36D02E2-C9F3-11CF-BFC7-444553540000}
pddoi->tszName: Wheel
pddoi->dwType: 1 (instance: 2)
pddoi->wUsage: 0 (page: 0)
StaticEnumObjectsCallback:
pddoi->guidType: {A36D02F0-C9F3-11CF-BFC7-444553540000}
pddoi->tszName: Button 0
pddoi->dwType: 4 (instance: 3)
pddoi->wUsage: 0 (page: 0)
StaticEnumObjectsCallback:
pddoi->guidType: {A36D02F0-C9F3-11CF-BFC7-444553540000}
pddoi->tszName: Button 1
pddoi->dwType: 4 (instance: 4)
pddoi->wUsage: 0 (page: 0)
StaticEnumObjectsCallback:
pddoi->guidType: {A36D02F0-C9F3-11CF-BFC7-444553540000}
pddoi->tszName: Button 2
pddoi->dwType: 4 (instance: 5)
pddoi->wUsage: 0 (page: 0)
StaticEnumObjectsCallback:
pddoi->guidType: {A36D02F0-C9F3-11CF-BFC7-444553540000}
pddoi->tszName: Button 3
pddoi->dwType: 4 (instance: 6)
pddoi->wUsage: 0 (page: 0)
StaticEnumObjectsCallback:
pddoi->guidType: {A36D02F0-C9F3-11CF-BFC7-444553540000}
pddoi->tszName: Button 4
pddoi->dwType: 4 (instance: 7)
pddoi->wUsage: 0 (page: 0)
StaticEnumDeviceCallback:
Skipping keyboard as input.
StaticEnumDeviceCallback:
pdidi->dwDevType: 11 (subtype: 0)
pdidi->tszProductName: HP Quick Launch Buttons

Log closed.
-----------------------------------------------

For the record, there haven't been any more crashes since the one I reported.

I know this is a low-priority issue for the helpline and appreciate your attention. Tyvm.

that_bloke · Post by **that_bloke** » Fri Nov 20, 2009 8:54 pm

i got the same thing tonight, someone suggested setting mip mapping to "auto" and that seemed to sort it, though when i told Fed i needed a min to sort something in menu he booted me!

Imago · Post by **Imago** » Mon Nov 23, 2009 11:36 am

Does changing the mip map setting have any effect?

RealPandemonium · Post by **RealPandemonium** » Mon Nov 23, 2009 4:52 pm

Imago wrote:QUOTE (Imago @ Nov 23 2009, 06:36 AM) Does changing the mip map setting have any effect?

I tried turning it on and off before and after launching from base. One of the times I did it, out of base texture colors returned to normal, but in-base they were still silhouettes. The problem persisted after that, and I was not able to reproduce the "fix" again. I cannot say whether the mip map settings had any effect, since my in-base textures are always silhouettes and sometimes the problem goes away on its own when out of base.

Allegiance has not crashed since the time of my original post. Thanks for your attention.

Imago · Post by **Imago** » Mon Nov 23, 2009 5:48 pm

I have a private build ready for you to try.
Use training mission 6 to confirm or deny it's fixed.
Extract to it's own folder and just double click Allegiance.exe.
Uses 1.0 key.

http://freeallegiance.sourceforge.net/pub/507x86.exe

RealPandemonium · Post by **RealPandemonium** » Tue Nov 24, 2009 5:00 am

Imago wrote:QUOTE (Imago @ Nov 23 2009, 12:48 PM) I have a private build ready for you to try.
Use training mission 6 to confirm or deny it's fixed.
Extract to it's own folder and just double click Allegiance.exe.
Uses 1.0 key.

http://freeallegiance.sourceforge.net/pub/507x86.exe

The issue did not manifest in the training mission. However, the training mission doesn't allow you to be in the loadout screen, which seems tied to the problem in some way. I'm trying to figure out how to set up my own server to try it, but am not very bright.

notjarvis · Post by **notjarvis** » Tue Nov 24, 2009 10:10 am

RealPandemonium wrote:QUOTE (RealPandemonium @ Nov 24 2009, 05:00 AM) The issue did not manifest in the training mission. However, the training mission doesn't allow you to be in the loadout screen, which seems tied to the problem in some way. I'm trying to figure out how to set up my own server to try it, but am not very bright.

Did you have the Beta server working?

If so - you may be able to copy Imagos exe into your beta folder (inside the alleg. one) and run it directly from there (Not through ASGS). Once in you should be able to create a game in the FazDev server.

Cortex · Post by **Cortex** » Tue Nov 24, 2009 6:04 pm

notjarvis wrote:QUOTE (notjarvis @ Nov 24 2009, 11:10 AM) If so - you may be able to copy Imagos exe into your beta folder (inside the alleg. one) and run it directly from there (Not through ASGS). Once in you should be able to create a game in the FazDev server.

It's not that easy, unfortunately, because Imago built it so that it uses the \1.0 registry key. (@Imago: please create beta builds to use the 1.1 key until we come up with a better solution for this problem.)

If you want to test and you're willing to jump through some hoops, the following steps should allow you to connect to the beta lobby with this build:
1. Start 'regedit' and go to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.0
2. Write down (or export/rename) the 'CfgFile' value, it should currently contain "http://autoupdate.alleg.net/allegiance.cfg"
3. Change the 'CfgFile' value to "http://fazdev.alleg.net/FAZ/FAZ.cfg" (that will make Alleg connect to the dev lobby).
4. Now start Allegiance.exe. Do not start ASGS. Do not click "Login" on ASGS.
5. After clicking on "games list", the MOTD should say "Welcome to the FAZDEV Server". Ignore the versions listed there.
6. Start a new game (select the core DN4.60, other cores might work or might not). Join a team. Click the checkbox in front of the other to deactivate it. Now you can start the game, despite being alone on the server.

Afterwards, change the 'CfgFile' value back to "http://autoupdate.alleg.net/allegiance.cfg" if you want to play via ASGS on the main lobby again. (That will only work with the official Allegiance.exe build. You can either restore it yourself, or wait for ASGS to notice it's an incorrect one and grab the correct one for you.)