<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to bugs</title><link href="https://sourceforge.net/p/newwolf/bugs/" rel="alternate"/><link href="https://sourceforge.net/p/newwolf/bugs/feed.atom" rel="self"/><id>https://sourceforge.net/p/newwolf/bugs/</id><updated>2013-04-28T06:37:54.686000Z</updated><subtitle>Recent changes to bugs</subtitle><entry><title>#1 Compiling with VC++ 6.0</title><link href="https://sourceforge.net/p/newwolf/bugs/1/?limit=25#f7ab" rel="alternate"/><published>2013-04-28T06:37:54.686000Z</published><updated>2013-04-28T06:37:54.686000Z</updated><author><name>David O'Shea</name><uri>https://sourceforge.net/u/doshea/</uri></author><id>https://sourceforge.net1346d137f44c44fe1d7baf23eb3621dc6d899c30</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;What were the linker errors you got?&lt;/p&gt;
&lt;p&gt;Passing "+goobers" on the command line causes the "goobers" console command to be executed once the game has started.  That command gives you full ammunition, weapons and keys (and maybe health), which is not exactly what you want - you just want to enable cheats, but that is not something you need to do via the command line.  All you need to do is start the game normally, then once you've actually selected a mission and difficulty level, hit the &lt;code&gt;key to display the console, type "god" and hit enter to enable god mode, then hit the&lt;/code&gt; key again to close the console.&lt;/p&gt;
&lt;p&gt;It seems to be a bug that if you pass any command on the command line other than "+set" - therefore including "+goobers" - and don't cause a map to be loaded using "+map &lt;map&gt;" or "+load ", you end up with this black screen.  "NewWolf.exe +map 1 +god" will start the game and automatically load map 1 and enter god mode, bypassing the startup screens and menu, without the black screen problem.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Music jumps around at random</title><link href="https://sourceforge.net/p/newwolf/bugs/4/" rel="alternate"/><published>2006-05-20T08:58:45Z</published><updated>2006-05-20T08:58:45Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net93bf46276da0ece460a360777784f6f295bc5b29</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Very often, the music currently playing will skip ahead&lt;br /&gt;
to another part of the song. Any idea as to what might&lt;br /&gt;
be causing it?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Borders around gfx patches</title><link href="https://sourceforge.net/p/newwolf/bugs/3/" rel="alternate"/><published>2005-10-22T22:51:52Z</published><updated>2005-10-22T22:51:52Z</updated><author><name>Schneelocke</name><uri>https://sourceforge.net/u/schneelocke/</uri></author><id>https://sourceforge.net626793238ef3cd6626864ecf572d269b138c1b0d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I've been experiencing a graphical glitch with NewWolf&lt;br /&gt;
for quite a while now that I never bothered to submit a&lt;br /&gt;
bug for, but I finally got fed up with it enough to do&lt;br /&gt;
so, so here you go:&lt;/p&gt;
&lt;p&gt;For some reason, graphics patches are drawn by the game&lt;br /&gt;
with a coloured border around them. For a demonstration&lt;br /&gt;
of this, please see these screenshots:&lt;/p&gt;
&lt;p&gt;Old (without glitch):&lt;br /&gt;
&lt;a href="http://schneelocke.net/images/mine/games/wolfenstein3d/nWolf10.png" rel="nofollow"&gt;http://schneelocke.net/images/mine/games/wolfenstein3d/nWolf10.png&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;New (with glitch):&lt;br /&gt;
&lt;a href="http://schneelocke.net/images/mine/games/wolfenstein3d/nWolf32.png" rel="nofollow"&gt;http://schneelocke.net/images/mine/games/wolfenstein3d/nWolf32.png&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Note that I'm also using the weapons model pack in the&lt;br /&gt;
old screenshot, but the glitch is not related to that;&lt;br /&gt;
I actually tried reinstalling NewWolf from scratch and&lt;br /&gt;
removing the model and texture packs, but it didn't&lt;br /&gt;
change anything.&lt;/p&gt;
&lt;p&gt;Since I know for a fact that things worked in the past&lt;br /&gt;
with the same NewWolf version, I do suspect that this&lt;br /&gt;
is related to the video driver (nVidia's Forceware, in&lt;br /&gt;
my case); it seems that at some point, an update of the&lt;br /&gt;
video driver uncovered a bug in NewWolf - or maybe vice&lt;br /&gt;
versa, but I don't really believe that, considering&lt;br /&gt;
that all other OpenGL games work just fine without any&lt;br /&gt;
glitches whatsoever.&lt;/p&gt;
&lt;p&gt;It'd be nice if you could investigate this; I'd&lt;br /&gt;
certainly be willing to help out with debugging,&lt;br /&gt;
testing etc., too, if I can. :)&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>You never die!</title><link href="https://sourceforge.net/p/newwolf/bugs/2/" rel="alternate"/><published>2005-08-20T00:53:45Z</published><updated>2005-08-20T00:53:45Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netec301df4bba91c4d3971ca5f41e62bd3ac857aed</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;If I die my last life and hit enter and then press&lt;br /&gt;
escape again, I restart exactly where I died, but with&lt;br /&gt;
0 health. I can then try to weasel myself out of that&lt;br /&gt;
situation. If I find health, it works great.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Compiling with VC++ 6.0</title><link href="https://sourceforge.net/p/newwolf/bugs/1/" rel="alternate"/><published>2004-06-03T18:37:02Z</published><updated>2004-06-03T18:37:02Z</updated><author><name>Bernhard Doebler</name><uri>https://sourceforge.net/u/bardware/</uri></author><id>https://sourceforge.net328509e9bdbc9e5de5ea52ab463090414680d820</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I just downloaded the source and wanted to compile it &lt;br /&gt;
myself. I simply tried the standard "Debug_Remote"-Build &lt;br /&gt;
and got some linker-Errors because of missing libraries. I &lt;br /&gt;
corrected the list of the libraries to link against to:&lt;br /&gt;
kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib &lt;br /&gt;
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib &lt;br /&gt;
opengl32.lib glu32.lib .\libs\libjpeg.lib winmm.lib&lt;br /&gt;
for Debug-Builds and to:&lt;br /&gt;
kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib &lt;br /&gt;
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib &lt;br /&gt;
opengl32.lib glu32.lib .\libs\___\jpeg.lib winmm.lib&lt;br /&gt;
for Release-Builds. That works fine for me.&lt;/p&gt;
&lt;p&gt;Why I downloaded the source...despite of playing &lt;br /&gt;
Wolf3D...I wanted to play in God-Mode. I read on the &lt;br /&gt;
internet I have to start the Wolf-executable with the &lt;br /&gt;
parameter "goobers". I didn't exactly understand how to &lt;br /&gt;
pass the parameter and nothing worked. Some websites &lt;br /&gt;
say I have to pass the parameters separated by a "-" &lt;br /&gt;
char to the EXE. Studying your code I finally found out &lt;br /&gt;
it's wrong (not your bad :-). The parameters must be &lt;br /&gt;
passed separated by a "+" (Plus-sign). Now something &lt;br /&gt;
happens when I start the game...but the screen stays &lt;br /&gt;
black...I in fact see the bar on the bottom of the screen &lt;br /&gt;
informing about health and ammo etc., I see the weapon &lt;br /&gt;
but I don't see walls and doors. Neither with your build &lt;br /&gt;
nor with my self-compiled exe. I don't want do delve so &lt;br /&gt;
deep into the code that I find out the reason myself...&lt;/p&gt;
&lt;p&gt;Can you explain how the game is intended to act when &lt;br /&gt;
the parameter "+goobers" is given?&lt;/p&gt;
&lt;p&gt;Best,&lt;br /&gt;
Bernhard&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>