I know its easier to post everything at once, but its much harder for Kryo and the devs to figure out what the issues are from a generic [BUG] titled post. That said, the FOW issue has been noted . The text bleed is well known, see here . For the CTD, the next time one happens, grab your dxdiag, the debug.err, and the dump zip and head over to the <a href="http://f
I know its easier to do a single post, but its much harder for Kryo to track errors. The CTD especially might be useful to put in the bug tracker as per the stickied guidelines .
This is exactly my issue here . The work around is to reduce the mipmap levels to 1. Also, post your debug.err file to pastebin.com and link to it, as per the sticky on guidelines . The missing graphics look an awful lot like the loading game issues (see this ). Are you loading a saved game at all?
Loading games is well-known to be fubar-ed . I don't think they planned to have it working yet.
Try lowering your resolution if possible, and reducing mipmap levels to 1. This is happening on a fresh game? No loading a saved game involved? Post your debug.err to pastebin.com in any case. If it's a new bug, you might want to open a new bug in the fogbugz tracker as per the sticky .
Agreed, this would help tremendously in preventing duplicate posts.
Just a suggestion: post your dxdiag and debug.err files on pastebin.com and just link to them here. Cleaner threads, and easier to see what's going on.
If it happens again, follow the instructions on the sticky and post the info with memory dump to the fogbugz tracker.
@Lomion Argarwaen, is it like mine or Strand's? (screen imprint or map imprint). Posting a pic would be nice, as would a debug.err link on pastebin I'll have to try actually playing a game with my imprints to see if it changes.
In the files there's a text section near the start that mentions Havok, so it's not just a standard .3DS or something. Definetly an importer/exporter thing. A Blender importer/exporter would be especially nice though.
DX9 vs DX10 is the first thing I notice there. ShadowDragon's machine in the other thread is also 9.0c The outline does seem to be WAD in my 1024x768 shots, except it only pops in after moving the camera once.
Post your debug.err file in My Documents\My Games\Elemental to pastebin.com and link to it from here. That's the information SD would find more useful. Also, does this happen every time? Does changing the video options make any difference? Sounds a bit similar to this issue.
If it happens again, post your debug.err on pastebin. It's much more useful.
Ah, good to know.
Also, seems to be the same issue as this . Does that sound right blackt1ger?
I believe a DirectX 9 card was the minimum required for video, which the 6200 is not the oldest of. Just make sure the drivers are new.
Your first shot looks a lot like Strand's here . Alt-tabbing is borked, as noted here . Similar transparent menus noted here . Btw, a suggestion: copy your debug.err to pastebin.com, and just link to it from here. The thread stays neater, and its a lot easier to see posts.
Your card should work as this page says it is a DirectX9 card, which is what is required I believe. As for drivers, that should be the correct one. The same drivers often work for multiple cards, and you can see the full list of cards supported in the release notes there. Don't worry about borking your computer, as that rarely happens anymore (if it does boot to safe mode and remove the driver via Add/Remov
@TheGreatTurtle You can open up the debug.err file in notepad or any other text editor. I'm guessing windows is saying there's no program installed for .err files, right? Just try to open it, and select notepad as the program to always use to open the file. The file's just plain text, so anyone can read it. Unless your debug.err is corrupted or something... that's a seperate issue.
The debug.err file is generated by running Elemental and contains some diagnostic information about your computer, and also lists information about how the program is actually running. This includes info like loading textures and game data and sound files, and lots of other internal game stuff that doesn't make much sense to us, but sure does to SD. You don't have to generate the report, it is automatically created each time you run the game. The file is located in My Docu
Take most of it back. I'm getting the same random crashes after changing options and sometimes not after changing options. Changing the prefs.ini by hand still seems to make it crash more consistently though.
Yeah, one of the other things with the mini-map not working yet (like the map itself :) Might want to edit the title of your post to make it a bit more obvious what the problem is from the main forum page.
For those who don't have issues, link to a normal debug.err on pastebin.com or something so we could tell some differences with those having issues.
This seems like one of the issues raised here . I don't think anyone's alt-tab works properly atm.
Is your issue similar to mine here ? I was clicking quickly at the start of the intro video, and I can do it pretty much every time. Btw, a suggestion: put your debug.err on pastebin.com or something and link to it. Makes this page much easier to read and quicker to see new posts.