Help
Duke4.net
DNF #1
Duke 3D #1
This topic is locked
Original post contents, merged into the wiki:
Spoiler
* Make sure the problem still happens with the latest development build as found there: http://dukeworld.duk...ke32/synthesis/
* If it does, and if the problem is a CRASH, please reproduce it using the debug versions of EDuke32 or Mapster32 found in the build (eduke32.debug.exe or mapster32.debug.exe). After you reproduce it, a file named "eduke32.crashlog" will be generated. Please make sure you attach it to your post.
Always do a search for your problem before posting. Any new topics should clearly describe the problem in the title/summary.
Please add the following information to any bug report
1) eduke32.log
2) mapster32.log
3) Your system specifications. (OS, GPU, CPU, etc)
4) What version of EDuke32 you are running.
5) What you were doing at the time.
6) Be ready to pm any modified con/sound/art/maps etc related to the above in the event an easy solution can't be found.
7) Go to http://dukeworld.duk...uke32/synthesis and find the first build that exhibits the problem, and post the build numbers of the last working version and the first broken version
This will help us and help you find solutions much more quickly and effectively. Any log files should be posted as attachments or loaded on to http://pastebin.com/.
Absolutely do NOT post logs as part of your post!
TerminX and Plagman should feel free to edit this topic and include any well known bugs.
* Make sure the problem still happens with the latest development build as found there: http://dukeworld.duk...ke32/synthesis/
* If it does, and if the problem is a CRASH, please reproduce it using the debug versions of EDuke32 or Mapster32 found in the build (eduke32.debug.exe or mapster32.debug.exe). After you reproduce it, a file named "eduke32.crashlog" will be generated. Please make sure you attach it to your post.
Always do a search for your problem before posting. Any new topics should clearly describe the problem in the title/summary.
Please add the following information to any bug report
1) eduke32.log
2) mapster32.log
3) Your system specifications. (OS, GPU, CPU, etc)
4) What version of EDuke32 you are running.
5) What you were doing at the time.
6) Be ready to pm any modified con/sound/art/maps etc related to the above in the event an easy solution can't be found.
7) Go to http://dukeworld.duk...uke32/synthesis and find the first build that exhibits the problem, and post the build numbers of the last working version and the first broken version
This will help us and help you find solutions much more quickly and effectively. Any log files should be posted as attachments or loaded on to http://pastebin.com/.
Absolutely do NOT post logs as part of your post!
TerminX and Plagman should feel free to edit this topic and include any well known bugs.
