Page 2 of 4
Posted: Fri Nov 20, 2009 9:53 am
by Cortex
notjarvis wrote:QUOTE (notjarvis @ Nov 20 2009, 08:57 AM) Ahhh - like sharpshooter and Death3D. My guess is this Gfx chipset is causing the problems. I believe Imago has a fix for this planned which will get released soon. Hold tight.
Not without data.
Imago wrote:QUOTE (Imago @ Nov 20 2009, 01:16 AM) What model of ATI? Post your VideoSettings.log into a
Code: Select all
[/quote]
^^^
PS: Wish you guys had tested the beta over the ~three months you had the chance to. Then this would have been fixed ages ago. :sad:
Posted: Fri Nov 20, 2009 10:35 am
by HSharp
notjarvis wrote:QUOTE (notjarvis @ Nov 20 2009, 07:57 AM) Ahhh - like sharpshooter and Death3D. My guess is this Gfx chipset is causing the problems. I believe Imago has a fix for this planned which will get released soon. Hold tight.
et tu notj?
---
Yup more beta testing would have been good but people are lazy and suck.
Posted: Fri Nov 20, 2009 11:01 am
by notjarvis
HSharp wrote:QUOTE (HSharp @ Nov 20 2009, 10:35 AM) et tu notj?
---
Yup more beta testing would have been good but people are lazy and suck.
Nah - I'm pretty fine - I actually tested my Intel Gfx configuration on the Beta - I occasionally went on for Beta flying but no-one was there
Cort - He's not got Ati Gfx - He got confused and changed what he posted as he was initially wrong. He has "VIA/S3G Unichrome IGP" gfx, which sounds similar to what Death3D and Startsailorare suffering from.
Edit : out of fear.
Posted: Fri Nov 20, 2009 11:07 am
by Cortex
HSharp wrote:QUOTE (HSharp @ Nov 20 2009, 11:35 AM) Yup more beta testing would have been good but people are lazy and suck.
I'm fine with people being lazy. What I'm not so fine with is when they then imply that the dev team has to drop everything else to solve *their* problems *immediately*. (Not you, Jagnara.)
Be lazy? Sure, then be patient!
notjarvis wrote:QUOTE (notjarvis @ Nov 20 2009, 12:01 PM) Cort - He's not got Ati Gfx - He got confused and changed what he posted as he was initially wrong. He has "VIA/S3G Unichrome IGP" gfx, which sounds similar to what Death3D and Sharpshooter are suffering from.
What's your point? He's not the only one, so someone else has to provide the dev team with the required information to fix it?
Posted: Sat Nov 21, 2009 6:13 am
by Jagnara
i apologize to the dev team for not participating in the beta testing. i was out of commission technologically at the time of testing, so i really had no opportunity to. but enough of that. youre right Cort: im not rushing anyone. if anything take your time. i want it done good. not fast. so w/e. im sure this isnt the first time that multiple players have had a major issue w/ one of alleg's updates (personally i hate updates b/c of the risk of having an issue like the one im having lol). but like i said before: i trust that the dev team will find a solution for our issue in time. which i have.
ty for your concern, Jagnara.
Posted: Sat Nov 21, 2009 8:32 am
by notjarvis
Jagnara wrote:QUOTE (Jagnara @ Nov 21 2009, 06:13 AM) ty for your concern, Jagnara.
As cort said - you can help the dev. team investigte this issue by posting the contents of your VideoSettings.log into a
Code: Select all
so they can see it.
You can find it in the alleg. directory (default = C:\Program Files\Microsoft Games\Allegiance)
Edit: P.S. An update to te gfx was necessary as newer Gfx cards were having trouble with the older engine we had before
Posted: Sat Nov 21, 2009 9:13 am
by Jagnara
Log file VideoSettings.log created - Nov 21, 02:03
Created D3D9 interface.
Found 1 adapters.
Extracting adapter 0: \\.\DISPLAY1 - VIA/S3G UniChrome IGP
800 x 600 @ 60Hz [32 bit] [HW 1 WND 1 DS 80 AA 0x01]
800 x 600 @ 75Hz [32 bit] [HW 1 WND 1 DS 80 AA 0x01]
800 x 600 @ 85Hz [32 bit] [HW 1 WND 1 DS 80 AA 0x01]
800 x 600 @ 100Hz [32 bit] [HW 1 WND 1 DS 80 AA 0x01]
1024 x 768 @ 60Hz [32 bit] [HW 1 WND 1 DS 80 AA 0x01]
1024 x 768 @ 75Hz [32 bit] [HW 1 WND 1 DS 80 AA 0x01]
1024 x 768 @ 85Hz [32 bit] [HW 1 WND 1 DS 80 AA 0x01]
1280 x 1024 @ 60Hz [32 bit] [HW 1 WND 1 DS 80 AA 0x01]
800 x 600 @ 60Hz [16 bit] [HW 1 WND 1 DS 80 AA 0x01]
800 x 600 @ 75Hz [16 bit] [HW 1 WND 1 DS 80 AA 0x01]
800 x 600 @ 85Hz [16 bit] [HW 1 WND 1 DS 80 AA 0x01]
800 x 600 @ 100Hz [16 bit] [HW 1 WND 1 DS 80 AA 0x01]
1024 x 768 @ 60Hz [16 bit] [HW 1 WND 1 DS 80 AA 0x01]
1024 x 768 @ 75Hz [16 bit] [HW 1 WND 1 DS 80 AA 0x01]
1024 x 768 @ 85Hz [16 bit] [HW 1 WND 1 DS 80 AA 0x01]
1280 x 1024 @ 60Hz [16 bit] [HW 1 WND 1 DS 80 AA 0x01]
FOUND RESOLUTIONS (MODE 0) (MAXRATE: 60):
0) 800x600 @ 60
1) 1024x768 @ 60
2) 1280x1024 @ 60
CURRENT IN-GAME RESOLUTION: 800x600 @ 60
User selected values:
AD 0 MON 0x00010001 WIN 1 VSYNC 0
Fullscreen settings:
FMT 22 W 800 H 600 RR 75 DEP 80
Windowed settings:
FMT 22 W 800 H 600 RR 75 DEP 80
FSMS 0 WINMS 0
MIN 3 MAG 3 MIP 2
Window offset: 0 0
Log closed.
here it is.
idk what this means; it's ugly.
im sure someone can use this. lol.
Posted: Sat Nov 21, 2009 11:21 pm
by Jagnara
^^bump
Posted: Mon Nov 23, 2009 11:31 am
by Imago
also post ur DeviceCreation,log too plz
Posted: Mon Nov 23, 2009 12:06 pm
by Imago
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/506x86.exe