Eggbird Posted August 9, 2012 Report Share Posted August 9, 2012 Hello,Not sure if this has already been reported by someone else. I did a quick search but did find anything. Although I doubt Im the only one who has this problem.When starting the Atlast Scenario Editor (the SVN version) my graphics card seems to crash (and recovers itself afterwards). After that Atlas seems to be running but the 3d part of the editor doesn't show up. Also, as soon as I try to use any of the other menu's it stops responding. Im not quite sure since when this problem occurs. I do know that several months ago everything was working fine.Here's a more accurate description of events:I double click on the shortcut '0 A.D. Editor SVN' which points to 'D:\0ad\binaries\system\Atlas.bat'At first, nothing really happens, than my mouse pointer freezes for a few seconds.My screen turns black for a second or soAfter the screen is back again I see the following notification:Next, Atlas looks like this:After trying to use Atlas, it freezes which looks like this:Other programs which were running at the same time and use the GFX card also are unusable after this and have to be killed (3d modeling applications and photoshop for example).I already tried rebooting and such but the problem always occurs again in the exact same way.Some specs about my PC:Processor: AMD Phenom II X6 1090T 3200MhzRAM: 16GBGFX: 2x AMD Radeon 6850 CrossFireOS: Windows 7 Professional 64 bitIm not sure if any logs are made during the above process and where I can find them. If you need any other info, let me know!The reason I want to use the Atlas scenario editor so badly is because I want to import and test the new Mauryan civic centre which im working on and is about to be finalized. Quote Link to comment Share on other sites More sharing options...
zoot Posted August 9, 2012 Report Share Posted August 9, 2012 Sounds strange/bad. I assume you have tried updating your GFX driver? That seems to be what crashed. Quote Link to comment Share on other sites More sharing options...
dvangennip Posted August 9, 2012 Report Share Posted August 9, 2012 I know this can be filed safely in the category, but anyway: have you tried recompiling everything or do you use the automatic builds of Atlas? Maybe some recent graphics changes have altered something which makes an older build of Atlas trip. Quote Link to comment Share on other sites More sharing options...
Eggbird Posted August 9, 2012 Author Report Share Posted August 9, 2012 Sounds strange/bad. I assume you have tried updating your GFX driver? That seems to be what crashed.Yep, Im on the latest Catalyst version (12.6). I did do a (simple) reinstall of the drivers and a reboot. But the issue persists.I don't seem to have any issues in other games or applications. Quote Link to comment Share on other sites More sharing options...
myconid Posted August 9, 2012 Report Share Posted August 9, 2012 I've been making some pretty heavy modifications to the rendering code lately, so maybe it's my fault. Pretty surprising that there's a driver crash, though.If you urgently need the editor, you can roll back the SVN a few revisions until you find one that works for you (try revision 12299). Do you know how to do that?Btw, if this fixes it then we'll need to do some debugging, when you have time. Thanks. (AFAIK you're the first Crossfire user to try this code) Quote Link to comment Share on other sites More sharing options...
historic_bruno Posted August 9, 2012 Report Share Posted August 9, 2012 Is this with the new experimental GLSL features enabled (AO, normal mapping, etc.) in the game's config file?Have you changed any Catalyst graphics settings (e.g. antialiasing or performance/quality) from their defaults? I suspect a driver reinstall would not reset those settings to defaults. I've had driver crashes in the past after altering those settings. Quote Link to comment Share on other sites More sharing options...
Eggbird Posted August 9, 2012 Author Report Share Posted August 9, 2012 Thx for the replies and remarks. I disabled crossfire after reading them and now everything works perfectly So somehow thats causing it. If you need me to do any extra research or something let me know, I'l gladly help! Quote Link to comment Share on other sites More sharing options...
myconid Posted August 10, 2012 Report Share Posted August 10, 2012 I'm seeing a lot of reports on the net that Crossfire/SLI tend to have some very serious issues with non-AAA games that aren't explicitly tested and supported by AMD/Nvidia (those reports also mention the driver crashing in exactly the way you described it). I suspect Crossfire support for OpenGL isn't too great, either.However, you say that a much older version of Atlas didn't have this problem. I'd like to find out exactly what OpenGL functionality causes the crash. When/if you get a chance, roll back the SVN history until you find a version of Atlas that works. Revision 12299 may be a good place to start. If you are able to get any debug output it could be useful, though I'm not too hopeful a driver crash like this would show on a debugger.All that having been said, the workaround seems pretty solid and very few people use Crossfire. I'd say this is a low-priority problem, so we shouldn't worry too much about it - at least at this point. Quote Link to comment Share on other sites More sharing options...
Eggbird Posted August 10, 2012 Author Report Share Posted August 10, 2012 idd, Im fine with disabling crossfire as a workaround. Its just a matter of changing a radio button and apply the change, no reboot required.Next week il try to find some time to find out which Atlas version is causing it. Il let you know if I have any news! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.