hi, im 'playing' nexuiz since vers. 1.1, 1.2 I do not remember exactly.
now I downloaded the new version and it runs worse here on my pc (xp 2400+, w2k, 9600pro 256mb, 768mb RAM)
Not alone that my framerate dropped extremly compared to the old versions, even with ALL effects disabled + the low.cfg settings, Nexuiz now hangs randomly (sometimes for a minute, sometimes I have to kill the pc with the reset-button) Alt+Tab or CTRL+Esc dont work either in such a situation. I tried both versions-sdl-version is even worse here-Unfortunatly it happens quite often, sometimes at the first match, sometimes I can play 1 or 2 matches before it hangs for an unknown reason. a sound (like the one by grabbing a weapon) is repeated all the time when this happens.....
And no, I don't expect to get any help here and I don't want to hear "ati sucks - nvidia rules" or "no problems here on my linux-system"-stories.
just wanted to say that I'm quite disappointed about how it evolved. I can't play anymore like this, its 2 annoying.

thanks for your time and hf anyway!

Well i'm sorry but what kind of answer to you expect from "i do not expect to get help".. If you followed this and the first forum you should know everyone here is trying to help each other but as noone here is near your PC most things are only speculation and ideas. And well yeah its also hard to think of some solutions if everything is working fine on ones own PC. Though it would be interesting to know if you changed something besides installing Nexuiz 2.0. Guess you do not want to hear but it should run as fine as 1.5 or 1.2.1 . Do you still have the older version installed? Does it still run without problems? Have you overwritten your old installation or have you used an other folder?

Could you please run Nexuiz with the startup option -condebug? That should produce a log file Nexuiz/data/qconsole.log and post this log file here? Maybe there is an error message or something. Your description is very much like "my car does not start" and i think no mechanic will be able to help you with that

Some other (general) things include watching the computers temperature. Its now getting very warm in most regions so this might be too much for some PC..

esteel wrote:Maybe there is an error message or something. Your description is very much like "my car does not start" and i think no mechanic will be able to help you with that

Yes he would... _if_ you brought the car

anyways. You are of cource running nexuiz-sdl.exe, not nexuiz.exe? try both. Overall I've experienced that 2.0 runs better on low settings than 1.5 did.

tChr wrote:Yes he would... _if_ you brought the car

Hehe, right but he did not bring his PC

Sorry if the "I do not expect to get help" did sound a bit weird, its just the truth. It's not that I think ppl in here aren't helpful or such a thing. I just don't think the problems I have can be solved with the usual suggestions. I've read them all, I'm following this board and also followed the old one. And yep, I'm aware of the fact that none of the forum users is sitting in front of my pc and therefor can't help much. I can't provide much more infos than I already did. I still have the nex 1.2 and 1.5 here on my pc, yep and the 1.5 is still running without problems. I did test that last night after a usual 2.0 crash. Sad thing is that one isn't able to use the "old" version on the new servers and to find populated 1.5 servers is quite hard, as it is to find populated nex servers in general (with reasonable pings). I didn't change anything on my pc before and after I installed nex 2.0.
I'm going to try the -condebug thing, but I doubt that it will help much if I have to reset my pc to be able to use it again.

It might be a heat problem, but then I wonder why it doesnt occur in other games that I'm playing (doom3, hl2, tremulous, ut, (nex 1.5)), my proz temperature is in his usual state around 56°C, can't say anything about the one from my gfx card, since it doesn't have sensors.

I didn't want to complain at all about the new nexuiz build , just wanted to say that not all is that great as most of the people here seem to like it to be.

Maybe,
-if you use linux,
-got a 4ghz pc 2gigs of ram and a nvidia card
-you don't care to play other games (that exists only in the windows world) and therefor did spend all your money to build your pc around this game)

you don't notice any bad things.

But I can assure you that, on my machine, the new version seems much more buggy than the old one.

It starts with being unable to minimize it, cause it comes back with a black screen only,
( And no, that isn't cause of poor memory management of winnt systems with memory below 1gig as urmel stated in another post. Sorry, but its kinda absurd, to blame the os for that. the poor memory management is to search @ the applications side itself, since these probs doesn't occur with commercial games which are using much more memory than nex (also Nexuiz 1.5 didnt got these probs at all))

and ends with crashes that I never had before with any other nexuiz version.

I really like the nexuiz gameplay and I think vermeulen did a great job developing it. No doubt there, but buying another pc or gfx card just to be able to run nexuiz is just a bit too much for me .

I will try to get a logfile anyhow..

@tChr: I tried both versions, not only the sdl-version as I stated already in my first post.

~>*

R4ND0M wrote:( And no, that isn't cause of poor memory management of winnt systems with memory below 1gig as urmel stated in another post. Sorry, but its kinda absurd, to blame the os for that. the poor memory management is to search @ the applications side itself, since these probs doesn't occur with commercial games which are using much more memory than nex (also Nexuiz 1.5 didnt got these probs at all))

I just have to answer that winnts mem management is kinda crappy, as it allows uses-space programs (if ther eis such a thing in WIN) far too much control...

However, My computer is not at all made for gaming, I just DLed nexuizs to test the 3D of my card once, and I've been playing since. I havent even ever upgraded my drivers since i first installed the PC. I'm also runnin XPsp2.

Good luyck with your problems. If you tell us where in the wold you are, maybe someone skilled will stop by one happy day?

I'm programming the windows api for some years and memory management is incumbent upon the programmer there. If one simply doesn't care, well, then such things might happen....

I just played nex 2.0 for some hours, I recompiled the source myself and it didn't crash. Strange thing, but actually I'm quite happy now

Hopefully it will stay like that from now on. I could still deserve some more frames, but it was playable at least.


cheers

im still using the -condebug param, if a crash occurs again I'm gonna paste it if possible.

R4ND0M wrote:I'm programming the windows api for some years and memory management is incumbent upon the programmer there. If one simply doesn't care, well, then such things might happen....

I just played nex 2.0 for some hours, I recompiled the source myself and it didn't crash. Strange thing, but actually I'm quite happy now

In case of the SDL build this can very well be true - 2.0 was released with an outdated libSDL because the current one has problems on non-US keyboards and a patch has yet to come (well, it IS in svn, but using an inofficially patched SDL isn't really a good idea either I think).

In case of the WGL build - this might actually be a problem with our build approach. We build automatically using mingw32, what did you use? Is it possible to trigger batch builds via network when using your build environment? It might help if you describe your exact build environment (compiler, DirectX header file version).

IF you get a crash on Windows, you probably get that problem report window. It might be a good idea to quote the exact error message with the register values, stack dump and the bytes around CS:EIP (you can display them from that dialog).

@divVerent:

I tried to compile with mingw/gcc using the dev-project files but got lots of linker errors. I managed to reduce them to a single warning -> "Warning: .drectve `/DEFAULTLIB:"uuid.lib" /DEFAULTLIB:"uuid.lib" ' unrecognized" but not further, so I tried the vc++ project, using vc++ toolkit 2003 along with linking the dinput.lib + dxguid.lib from the directx9 sdk which finally compiled. I didn't try to the sdl-version yet.
what do you mean with trigger batch?
I didnt get an error message with a stack dump, I did only see the error window when using nexuiz-sdl.exe and then there was only a message that nex-sdl created a failure and was closed. I was unable to locate a logfile with further infos, maybe this service isn't activated here.

in fact, Windows XP is able to display a problem report like we want it:

in the "send problem report" dialog, there is a blue link. Click it. In the then appearing dialog, there are two blue links. Click the first one. This is what we want.

Only problem: that dialog item is disabled and not just read only, meaning that it's impossible to copypaste from there. Windows sucks - and this really shows it. To get useful information, you have to enter control panel, then administration, then event log, then look in the application event log for DrWatson reports about Nexuiz. Click the copy button in that dialog and post the whole report somewhere. You should decode it to something readable first, this can be done in vim+perl like this:

:%!perl -pe '/: (..) .. (..) .. (..) .. (..)/ and $_ = join "", map chr, hex$1, hex$2, hex$3, hex$4'

If you can't, send the full report to me as private message and I will decode it.

"in fact, Windows XP is able to display a problem report like we want it:..."

Im on win2000pro and already checked the event log without success. There is no "send problem report"-dialog on w2k so there is no blue link either I remember that I kicked drwatsons ass some months back (i read that he happily collects garbage) so I disabled something. Maybe it was the logging part, dunno.

but it seems that my problem is solved, I just played again 4-5 maps in a row and no crash occurs, so I'm quite optimistic that the recompilation did the trick, thx. you didnt say what you meant with the batch trigger-thingy?

R4ND0M wrote:but it seems that my problem is solved, I just played again 4-5 maps in a row and no crash occurs, so I'm quite optimistic that the recompilation did the trick, thx. you didnt say what you meant with the batch trigger-thingy?

A method to start the build from another computer. Without owning a free computer for Windows in my case...

[quote="divVerent"]
A method to start the build from another computer. Without owning a free computer for Windows in my case...[/quote]

Oh, ok, nope thats not possible here.

today I compiled the darkplaces-sdl sources with newest sdl libs and running the exe gives me nearly stable 85fps which is my mon refresh rate. So I would recommend everyone who is using the sdl version to (re-)compile it on his own.

Well that hint is fine but i find it harder to do this on windows then on linux.. Especialy if people are not developers and have no clue about Dev-C++ or MinGw. (So they do not have to buy something just to compile DP..)
For that reason we have to find out whats wrong with the official build and fix it!

>Especialy if people are not developers and have no clue about Dev-C++ or MinGw. (So they do not have to buy something just to compile DP..)

yup, you are right there for sure esteel, there are enough free tools available nowadays though (mingw/gcc, vc++ 2k3 toolkit and visualstudio express edition ( http://blogs.msdn.com/danielfe/archive/ ... 79109.aspx )which is now free to use even if you want to use it to build commercial apps (as far as I understood).

But I agree that not everyone is willing to/experienced enough to build darkplaces himself. Just wanted to report that it helped me doing it.

R4ND0M wrote:yup, you are right there for sure esteel, there are enough free tools available nowadays though (mingw/gcc, vc++ 2k3 toolkit and visualstudio express edition ( http://blogs.msdn.com/danielfe/archive/ ... 79109.aspx )which is now free to use even if you want to use it to build commercial apps (as far as I understood).

Add to this that the mingw32 build is making trouble for one poster here while a Visual Studio build isn't... for that reason I'd really like to know what's wrong with my mingw32 installation. Can you try building on Dev-C++ or mingw32+msys in the current versions and check if that build is better? In that case, I'd replace my mingw32 version by that very version and check if it's better then.

@divVerent:

As I said earlier, I didnt manage to compile the dev-c++ project due to this warning "Warning: .drectve `/DEFAULTLIB:"uuid.lib" /DEFAULTLIB:"uuid.lib" ' unrecognized". I wasn't able to spot any pragma comment or something which contains this in the sources, if you tell me how to get rid of the warning I could try it again.

How about mingw/msys installation then?
I think i have the latest version installed at home so i might compile a binary later. But sofar i only tried to compile the wgl version. Never bother with getting the sdl version to compile..

R4ND0M wrote:@divVerent:

As I said earlier, I didnt manage to compile the dev-c++ project due to this warning "Warning: .drectve `/DEFAULTLIB:"uuid.lib" /DEFAULTLIB:"uuid.lib" ' unrecognized". I wasn't able to spot any pragma comment or something which contains this in the sources, if you tell me how to get rid of the warning I could try it again.

My idea would be ignoring the Dev-C++ project and compiling using the Makefile, given you have programs named "make" and "sh". If you don't, these are in MSYS.

Ok i comiled a binary: http://esteel.planetnexuiz.de/nexuiz/misc/nexuiz.exe
I (think) have installed: MSYS-1.0.10.exe, MinGW-3.1.0-1.exe

Glad to hear that Nexuiz now is working for you R4ND0M. What u wrote makes me wanna try to make a build on my own, as i could use some more FPS..
I must admit i have never compiled anything, yet , so maybe u could give me and all others that wanna try some tips how to compile Nexuiz under Windows?

Its not that much work.. download and install MSYS-1.0.10.exe, MinGW-3.1.0-1.exe from mingw.org. download the original quake1 sources OR the DirectX SDK (you just need some header files, the q1 sources are smaller and less MS ) and put those header files into your MingGW installation (its been some time.. copying them into MINGW/include should be it). Then you need the DarkPlaces souces either from cvs or the included sources in Nexuiz. Now a simple 'make DP_MAKE_TARGET=mingw cl-nexuiz' in the DP source dir should be enough to produce a binary.
*edit* corrected make target

Thanks for your help esteel.
When i try to compile i get the following errors:

Code: Select all

sys_sdl.o(.text+0x127):sys_sdl.c: undefined reference to `SDL_GetTicks'
sys_sdl.o(.text+0x1b):sys_sdl.c: undefined reference to `SDL_Quit'
sys_sdl.o(.text+0x29f):sys_sdl.c: undefined reference to `SDL_Delay'
vid_sdl.o(.text+0x5a):vid_sdl.c: undefined reference to `SDL_WM_GrabInput'
vid_sdl.o(.text+0x93):vid_sdl.c: undefined reference to `SDL_WM_GrabInput'
vid_sdl.o(.text+0xcd):vid_sdl.c: undefined reference to `SDL_GetRelativeMouseSta                                             te'
vid_sdl.o(.text+0x175):vid_sdl.c: undefined reference to `SDL_PollEvent'
vid_sdl.o(.text+0x2c9):vid_sdl.c: undefined reference to `SDL_Init'
vid_sdl.o(.text+0x2e6):vid_sdl.c: undefined reference to `SDL_GetError'
vid_sdl.o(.text+0x30f):vid_sdl.c: undefined reference to `SDL_WM_SetCaption'
vid_sdl.o(.text+0x326):vid_sdl.c: undefined reference to `SDL_GetWMInfo'
vid_sdl.o(.text+0x3b6):vid_sdl.c: undefined reference to `SDL_Linked_Version'
vid_sdl.o(.text+0x4d1):vid_sdl.c: undefined reference to `SDL_SetVideoMode'
vid_sdl.o(.text+0x502):vid_sdl.c: undefined reference to `SDL_GL_LoadLibrary'
vid_sdl.o(.text+0x555):vid_sdl.c: undefined reference to `SDL_GL_SetAttribute'
vid_sdl.o(.text+0x56c):vid_sdl.c: undefined reference to `SDL_GL_SetAttribute'
vid_sdl.o(.text+0x577):vid_sdl.c: undefined reference to `SDL_GL_SetAttribute'
vid_sdl.o(.text+0x582):vid_sdl.c: undefined reference to `SDL_GL_SetAttribute'
vid_sdl.o(.text+0x58d):vid_sdl.c: undefined reference to `SDL_GL_SetAttribute'
vid_sdl.o(.text+0x598):vid_sdl.c: more undefined references to `SDL_GL_SetAttrib                                             ute' follow
vid_sdl.o(.text+0x5b5):vid_sdl.c: undefined reference to `SDL_SetVideoMode'
vid_sdl.o(.text+0x5c6):vid_sdl.c: undefined reference to `SDL_GetError'
vid_sdl.o(.text+0x5fe):vid_sdl.c: undefined reference to `SDL_SetEventFilter'
vid_sdl.o(.text+0x60a):vid_sdl.c: undefined reference to `SDL_EnableUNICODE'
vid_sdl.o(.text+0x618):vid_sdl.c: undefined reference to `SDL_EnableKeyRepeat'
vid_sdl.o(.text+0x6b7):vid_sdl.c: undefined reference to `SDL_GL_SetAttribute'
vid_sdl.o(.text+0x6c2):vid_sdl.c: undefined reference to `SDL_GL_SetAttribute'
vid_sdl.o(.text+0x6cd):vid_sdl.c: undefined reference to `SDL_GL_SetAttribute'
vid_sdl.o(.text+0x6fb):vid_sdl.c: undefined reference to `SDL_GetError'
vid_sdl.o(.text+0x735):vid_sdl.c: undefined reference to `SDL_QuitSubSystem'
vid_sdl.o(.text+0x756):vid_sdl.c: undefined reference to `SDL_SetGammaRamp'
vid_sdl.o(.text+0x786):vid_sdl.c: undefined reference to `SDL_GetGammaRamp'
vid_sdl.o(.text+0x7c9):vid_sdl.c: undefined reference to `SDL_GetAppState'
vid_sdl.o(.text+0x6c):vid_sdl.c: undefined reference to `SDL_ShowCursor'
vid_sdl.o(.text+0x295):vid_sdl.c: undefined reference to `SDL_GL_GetProcAddress'
vid_sdl.o(.text+0x8e1):vid_sdl.c: undefined reference to `SDL_GL_SwapBuffers'
snd_sdl.o(.text+0x390):snd_sdl.c: undefined reference to `SDL_InitSubSystem'
snd_sdl.o(.text+0x453):snd_sdl.c: undefined reference to `SDL_OpenAudio'
snd_sdl.o(.text+0x462):snd_sdl.c: undefined reference to `SDL_GetError'
snd_sdl.o(.text+0x4ad):snd_sdl.c: undefined reference to `SDL_CloseAudio'
snd_sdl.o(.text+0x521):snd_sdl.c: undefined reference to `SDL_PauseAudio'
snd_sdl.o(.text+0x566):snd_sdl.c: undefined reference to `SDL_CloseAudio'
snd_sdl.o(.text+0x5e6):snd_sdl.c: undefined reference to `SDL_LockAudio'
snd_sdl.o(.text+0x605):snd_sdl.c: undefined reference to `SDL_UnlockAudio'
cd_sdl.o(.text+0x25):cd_sdl.c: undefined reference to `SDL_CDStatus'
cd_sdl.o(.text+0x5e):cd_sdl.c: undefined reference to `SDL_CDEject'
cd_sdl.o(.text+0xe7):cd_sdl.c: undefined reference to `SDL_CDStop'
cd_sdl.o(.text+0x11f):cd_sdl.c: undefined reference to `SDL_CDPlayTracks'
cd_sdl.o(.text+0x151):cd_sdl.c: undefined reference to `SDL_CDStop'
cd_sdl.o(.text+0x16d):cd_sdl.c: undefined reference to `SDL_CDStatus'
cd_sdl.o(.text+0x183):cd_sdl.c: undefined reference to `SDL_CDPause'
cd_sdl.o(.text+0x1ae):cd_sdl.c: undefined reference to `SDL_CDResume'
cd_sdl.o(.text+0x20e):cd_sdl.c: undefined reference to `SDL_CDPlayTracks'
cd_sdl.o(.text+0x267):cd_sdl.c: undefined reference to `SDL_CDStatus'
cd_sdl.o(.text+0x35c):cd_sdl.c: undefined reference to `SDL_InitSubSystem'
cd_sdl.o(.text+0x4a6):cd_sdl.c: undefined reference to `SDL_CDNumDrives'
cd_sdl.o(.text+0x4e6):cd_sdl.c: undefined reference to `SDL_CDOpen'
cd_sdl.o(.text+0x525):cd_sdl.c: undefined reference to `SDL_CDOpen'
cd_sdl.o(.text+0x555):cd_sdl.c: undefined reference to `SDL_CDOpen'
cd_sdl.o(.text+0x5ab):cd_sdl.c: undefined reference to `SDL_CDStatus'
cd_sdl.o(.text+0x5d4):cd_sdl.c: undefined reference to `SDL_CDClose'
cd_sdl.o(.text+0x5f5):cd_sdl.c: undefined reference to `SDL_CDStatus'
cd_sdl.o(.text+0x622):cd_sdl.c: undefined reference to `SDL_CDClose'
cd_sdl.o(.text+0x645):cd_sdl.c: undefined reference to `SDL_CDStatus'
cd_sdl.o(.text+0x672):cd_sdl.c: undefined reference to `SDL_CDClose'
cd_sdl.o(.text+0x6b7):cd_sdl.c: undefined reference to `SDL_CDClose'
cd_sdl.o(.text+0x756):cd_sdl.c: undefined reference to `SDL_CDNumDrives'
cd_sdl.o(.text+0x7ad):cd_sdl.c: undefined reference to `SDL_CDOpen'
cd_sdl.o(.text+0x7d5):cd_sdl.c: undefined reference to `SDL_CDStatus'
cd_sdl.o(.text+0x81b):cd_sdl.c: undefined reference to `SDL_CDClose'
c:/MinGW/bin/../lib/gcc-lib/mingw32/3.2.3/../../../libmingw32.a(main.o)(.text+0x                                             97):main.c: undefined reference to `WinMain@16'
make[3]: *** [nexuiz-sdl.exe] Error 1
make[3]: Leaving directory `/c/Downloads/Nexuiz/make/darkplaces'
make[2]: *** [bin-release] Error 2
make[2]: Leaving directory `/c/Downloads/Nexuiz/make/darkplaces'
make[1]: *** [sdl-nexuiz] Error 2
make[1]: Leaving directory `/c/Downloads/Nexuiz/make/darkplaces'
make: *** [nexuiz] Error 2


I think i have all the headers from the quake source (q1\WinQuake and q1\WinQuake\dxsdk\SDK\INC). I also copied all the headers from nexuiz/Nexuiz-SDL.app\Contents\Frameworks\SDL.framework\Versions\A\Headers to MinGW/include as there were some of them requested during make and i did not find them in the quake source. But the errors above remain. Any suggestions?

Ah sorry.. I never bothered to get the sdl version to build.. the wgl (nexuiz.exe) should build though with 'make DP_MAKE_TARGET=mingw cl-nexuiz'

yes the nexuiz.exe did built . But i cant say yet, if it is faster than the precompiled or not...i think would be interesting to know.

EDIT:
I did timedemo several times on each build and the results were the same.

Well the problem for R4ND0M was a crash that was fixed by compiling DP himself. I just hope we can find the cause so that future versions of Nexuiz do not crash. Having to compile something because of such an error is ugly!
As i wrote in some other thread its very unlikely that DP gets faster by compiling it with some options. It already very fast but it still seems to have problems with some cards/drivers..

Hmm can someone tell my why some edits show the line *last edited..* and some do not?

dIM wrote:Thanks for your help esteel.
When i try to compile i get the following errors:

Code: Select all

sys_sdl.o(.text+0x127):sys_sdl.c: undefined reference to `SDL_GetTicks'

Just do "make cl-nexuiz" - then you won't need the SDL stuff.

@dIM:

http://www.libsdl.org/release/SDL-devel ... w32.tar.gz

I used these libs (the vc 6 version of them tho) to build the nexuiz-sdl.exe. You will need to exchange the sdl.dll from the nex-dir with the one from the newer version too.

hope this helps

R4ND0M wrote:@dIM:

http://www.libsdl.org/release/SDL-devel ... w32.tar.gz

Is that one still broken with respect to international keyboards or can I use it?

I have no idea, didn't test them yet. the vc6 version from that page is running well.

For my dev-c++ installation I got a sdl version from here: http://devpaks.org/category.php?category=SDL.