Re: Zandronum 3.0-alpha-170416-0710
Posted: Tue Apr 18, 2017 7:20 pm
They weren't having the issue before TSPG changed their servers to 3.0, and the moment they switched over they started getting this issue.
Leading the way in newschool multiplayer Doom online
https://zandronum.com/forum/
With "this issue" you are referring to the connection problems, which are likely caused by a non-default setting of sv_maxpacketsize on TSPG? The OpenGL thread you linked seems to be almost a month old, so this can't have to do with the recent change on TSPG, right?Cutman wrote:They weren't having the issue before TSPG changed their servers to 3.0, and the moment they switched over they started getting this issue.
There are differences in OpenGL in 2.1.2 and 3.0, so it's possible that they behave differently. Going back to 2.1.2 fixes the problem for the two? And 3.0 never worked for them or they never tried it before? Can you open a ticket for this issue and have them post their console log with all the OpenGL info displayed by 2.1.2 and 3.0 on their systems?Cutman wrote:Oops! Sorry, I was referring to the OpenGL slowdown. Two people started getting slowdown as soon as they started using 3.0 (only in openGL).
I've posted a ticket with logs from both people. https://zandronum.com/tracker/view.php?id=3074Torr Samaho wrote:Can you open a ticket for this issue and have them post their console log with all the OpenGL info displayed by 2.1.2 and 3.0 on their systems?
Thanks for the reminder, I lost track of that.Combinebobnt wrote:torr review (approve ) rust's ticket it's done but fell in the dust bin:
https://zandronum.com/tracker/view.php?id=1814
Now imagine what I think when I'm supposed to debug these problems without a minimal example ;).Combinebobnt wrote:edit: UGH these bugs without minimal example wads how the hell am I supposed to test
So far I never provided raspi binaries. Can you compile Zandronum yourself? Compilation of the current 3.0 source should work without any changes to the source code. I tested it on a raspi 2.grrfield wrote:Ready to test those out. Where can I find the files for the raspberry pi (if these have been made/prepared, ofc)?
Thank you for your reply.Torr Samaho wrote:So far I never provided raspi binaries. Can you compile Zandronum yourself? Compilation of the current 3.0 source should work without any changes to the source code. I tested it on a raspi 2.grrfield wrote:Ready to test those out. Where can I find the files for the raspberry pi (if these have been made/prepared, ofc)?
We only have tags for the stable versions, that's why you end up compiling 2.1.2 when following the guide. Replace the hg update command withgrrfield wrote: Last time I tried compiling 3.0, I followed the instructions on https://wiki.zandronum.com/Compiling_th ... spberry_Pi, but everytime I ended up with compiling 2.1.2. I am a bit confused on how to get the 3.0 code on my machine (and maybe other stuff I may be doing wrong). It does not surprise me entirely that it is not working, since the most recent tag I find on that bitbucket is ZA_2.1.2 (which "maxtagged" will use ..... I guess). A little guidance would be much appreciated here....
Code: Select all
hg update df61f80660cc64a71d4bffff53e29e3c79860d40
When compiling it on a raspberry pi 3B+ I end up with the following at the very end:Torr Samaho wrote:We only have tags for the stable versions, that's why you end up compiling 2.1.2 when following the guide. Replace the hg update command withgrrfield wrote: Last time I tried compiling 3.0, I followed the instructions on https://wiki.zandronum.com/Compiling_th ... spberry_Pi, but everytime I ended up with compiling 2.1.2. I am a bit confused on how to get the 3.0 code on my machine (and maybe other stuff I may be doing wrong). It does not surprise me entirely that it is not working, since the most recent tag I find on that bitbucket is ZA_2.1.2 (which "maxtagged" will use ..... I guess). A little guidance would be much appreciated here....and you should have the code corresponding to Zandronum 3.0-alpha-170416-0710. You should also skip applying the patch mentioned in the Wiki. 3.0 doesn't need it. If you encounter any problems, just let me know.Code: Select all
hg update df61f80660cc64a71d4bffff53e29e3c79860d40
Code: Select all
[ 99%] Building CXX object src/CMakeFiles/zdoom.dir/zzautozend.o
[ 99%] Linking CXX executable ../zandronum-server
CMakeFiles/zdoom.dir/tempfiles.o: In function `FTempFileName::FTempFileName(char const*)':
/home/pi/zandronum-build/zandronum/src/tempfiles.cpp:46: warning: the use of `tempnam' is dangerous, better use `mkstemp'
Creating 'zandronum-server.debug' ...
/bin/sh: 1: --only-keep-debug: not found
src/CMakeFiles/zdoom.dir/build.make:9510: recipe for target 'zandronum-server' failed
make[2]: *** [zandronum-server] Error 127
make[2]: *** Deleting file 'zandronum-server'
CMakeFiles/Makefile2:1032: recipe for target 'src/CMakeFiles/zdoom.dir/all' failed
make[1]: *** [src/CMakeFiles/zdoom.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
pi@grrfield:~/zandronum-build/zandronum $
Thanks! Now we just need people to supply the missing minimal example wads for the other tickets ;). Any volunteers?Combinebobnt wrote:ok torr I tested every single ticket that isn't random dusk code or edward san's no examples or that raspberry pi and sql crap (and good lord that damagefactor ticket the hell is he trying to communicate).
I'm glad to hear that it works now!grrfield wrote:Don't worry, a friend of mine, with more skills compiled it for me.
Thanks anyway
Looks like your compiler or cmake has a problem trying to figure out whether the flag "-msse" is supported on your system.mentaluproar wrote:I've no idea what's wrong. You?
Code: Select all
if( "${CMAKE_CXX_COMPILER_ID}" STREQUAL "GNU" OR "${CMAKE_CXX_COMPILER_ID}" STREQUAL "Clang" )
CHECK_CXX_COMPILER_FLAG( -msse DUMB_CAN_USE_SSE )
if( DUMB_CAN_USE_SSE )
set_source_files_properties( src/it/filter.cpp PROPERTIES COMPILE_FLAGS -msse )
endif( DUMB_CAN_USE_SSE )
endif( "${CMAKE_CXX_COMPILER_ID}" STREQUAL "GNU" OR "${CMAKE_CXX_COMPILER_ID}" STREQUAL "Clang" )
Let's better discuss the technical details on the tracker.mentaluproar wrote:Is this helpful or should I move this to the tracker?