Shana Posted February 15, 2014 Author Posted February 15, 2014 Here is why et pro does not work on ET L 2.71rc3 -------- UNRECOVERABLE ERROR -------- This may be due to a bug in etpro Information to be used in a bug report is being generated: ------------- CUT HERE -------------- Version: etpro 3.2.6 Platform: Linux Build: Sep 16 2006 18:02:39 Signal: Segmentation violation (11) Signal code: 1 fault address: 0xfffffc4d Load addresses: 0xf778f000 linux-gate.so.1 0xf7761000 /lib32/libdl.so.2 0xf773a000 /lib32/libm.so.6 0xf7731000 /lib32/librt.so.1 0xf7717000 /lib32/libpthread.so.0 0xf7695000 /usr/lib32/libGLU.so.1 0xf7632000 /usr/lib32/libGL.so.1 0xf762a000 /usr/lib32/libSM.so.6 0xf7612000 /usr/lib32/libICE.so.6 0xf74f7000 /usr/lib32/libX11.so.6 0xf74e8000 /usr/lib32/libXext.so.6 0xf735f000 /lib32/libc.so.6 0xf7790000 /lib/ld-linux.so.2 0xf7277000 /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libstdc++.so.6 0xf725b000 /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so.1 0xf7229000 /usr/lib32/libglapi.so.0 0xf7225000 /usr/lib32/libXdamage.so.1 0xf721e000 /usr/lib32/libXfixes.so.3 0xf721b000 /usr/lib32/libX11-xcb.so.1 0xf7207000 /usr/lib32/libxcb-glx.so.0 0xf71ec000 /usr/lib32/libxcb.so.1 0xf71e6000 /usr/lib32/libXxf86vm.so.1 0xf71da000 /usr/lib32/libdrm.so.2 0xf71d5000 /lib32/libuuid.so.1 0xf71d1000 /usr/lib32/libXau.so.6 0xf71cb000 /usr/lib32/libXdmcp.so.6 0xed914000 /lib32/libnss_compat.so.2 0xed8fd000 /lib32/libnsl.so.1 0xf777f000 /lib32/libnss_nis.so.2 0xf7773000 /lib32/libnss_files.so.2 0xec0f3000 /usr/lib32/libXrender.so.1 0xec0e9000 /usr/lib32/libXrandr.so.2 0xebf12000 /usr/lib32/libXcursor.so.1 0xebd71000 /usr/lib32/dri/i965_dri.so 0xeba27000 /usr/lib32/libdricore9.0.0.so.1 0xeb9fd000 /usr/lib32/libexpat.so.1 0xeb9dd000 /usr/lib32/libdrm_intel.so.1 0xeb9d3000 /usr/lib32/libpciaccess.so.0 0xeb9be000 /lib32/libz.so.1 0xea939000 /usr/lib32/libasound.so.2 0xea9fb000 /usr/lib32/alsa-lib/libasound_module_rate_speexrate.so 0xea900000 /usr/lib32/libspeexdsp.so.1 0xde571000 /lib32/libnss_dns.so.2 0xde55c000 /lib32/libresolv.so.2 0xdb503000 /home/morsik/.etlwolf.clean//etpro/qagame.mp.i386.so 0xdfc8a000 /home/morsik/.etlwolf.clean//etpro/ui.mp.i386.so 0xd46ee000 /home/morsik/.etlwolf.clean//etpro/cgame.mp.i386.so EIP: 08143b00 edi:d47d7d64 esi:ff82be40 ebp:ff82c270 esp:ff82bdbc eax:fffffc4d ebx:d47c89d4 ecx:08143b00 edx:ff82c2db stack: d46f8536 ff82c270 00000482 ff82be60 08060535 ff82be60 ff82be60 fffffc4d ffdf8e50 9e1547ed 57ec91c2 30fa8bc8 c7785a54 a7efa5e3 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 code: 00 00 00 c1 f8 08 01 45 90 8b 45 8c 8b 55 9c 89 d1 29 c1 89 c8 0f af 45 a8 05 ff 00 00 00 c1 f8 08 01 45 8c 8b 45 88 8b 55 98 89 d3 29 c3 89 d8 0f af 45 a8 Stack trace: 1 entries /home/morsik/.etlwolf.clean//etpro/cgame.mp.i386.so(+0x1df22)[0xd470bf22] ------------- CUT HERE -------------- Trying to clean up... ----- CL_Shutdown ----- Favourite servers saved: 0 Sys_LoadDll(/home/morsik/.etlwolf.clean//etpro/ui.mp.i386.so)... succeeded Sys_LoadDll(ui) found vmMain function at 0xdfc907d0 Favourite servers restored: 0 Closing SDL audio device... SDL audio device shut down. RE_Shutdown( 1 ) Favourite servers saved: 0 ----------------------- ----- Server Shutdown ----- ==== ShutdownGame ==== --------------------------- Segmentation fault Quote
Clan Friend SunLight Posted February 15, 2014 Clan Friend Posted February 15, 2014 etpro requires et260b, and checks if you have it. It's normal that it fails. It's perfectly possible to make a new ET compatible with etpro. I made it in a beta version of my demoviewer I never released, and in that custom ET to show hitboxes (the one we used in that old thread about etpro hitboxes here in this forum). It's up to them if they want to do it, but obviously it requires changes in etpro, and I maybe it would be a problem if they have to release the source code of that thing What's more (imho) in a fair game all players should play with the same version of the game (and possibly the same settings). On etpro servers all have 2.60b and that is ok. Quote
Shana Posted February 15, 2014 Author Posted February 15, 2014 By far it's little bit harder to play on et l Also they are trying to 'revive' et to it's old state. All those updates are for something. Maybe the first patches won't be so good. I guess when they continue developing et it might get something good out of it. I rather enjoy playing on 'normal' et version because in the future it can change Th3o Quote
staticwarp Posted March 11, 2014 Posted March 11, 2014 (edited) hey the0ry, i've got an et:l question for you. et legacy does a great job of detecting and setting the best resolution when you first install it, but if it gets changed for some reason is there a way to re-do the auto detect that happens during install? i'm trying to get the resolution right with et:l on a new laptop and the usual commands make it crash. since i couldn't figure out a way to re-run the auto resolution detect that et:l does during install, i tried the old method of getting a custom resolution. i ran the following in the console: seta r_customwidth 1382 seta r_customheight 768 seta r_customaspect 1 seta r_mode -1 this produces a crash. i did a writeconfig before changing anything and i noticed that et:l lists r_mode as being "unsafe" and it is marked as such on the default et:l config. r_customaspect probably is as well. since these two cvars don't work with et:l, how can we manually enter a custom resolution in the console? edit: ok nvm! i went to put the error log up at pastebin and i noticed that the console lists the available modes before setting the custom resolution. 1382/768 is not supported, but 1366/768 is. i used 1366/768 instead and et:l doesn't crash. my resolution is fixed now. it would be cool if you could run the autodetect at any time in case you switch displays a lot. i'll have to mention it on their forum. i also noticed that the upside down cursor i was talking about earlier only appears after i play on an fa server. interesting. Edited March 11, 2014 by staticwarp Quote
herpderp Posted March 11, 2014 Posted March 11, 2014 seriously, if you have fps issues in et, there's a bigger problem. i had 76-125 fps on a p4 years ago that being said, ill give this a look tomorrow. kinda curious about it Quote
dUUUmzz Posted March 12, 2014 Posted March 12, 2014 Does more than stable 125fps help something too? I mean for example in COD4 125fps vs 250 were huge differents. With 250 stable fps it was much easyer to move and do some bounce and trickjumps Quote
Arkinder Posted March 12, 2014 Posted March 12, 2014 etpro requires et260b, and checks if you have it. It's normal that it fails. It's perfectly possible to make a new ET compatible with etpro. I made it in a beta version of my demoviewer I never released, and in that custom ET to show hitboxes (the one we used in that old thread about etpro hitboxes here in this forum). It's up to them if they want to do it, but obviously it requires changes in etpro, and I maybe it would be a problem if they have to release the source code of that thing What's more (imho) in a fair game all players should play with the same version of the game (and possibly the same settings). On etpro servers all have 2.60b and that is ok. ET Pro uses hooks to function in the first place. The seg fault above is a result of ET Pro trying to use memory locations that have not been allocated to it. ET Pro is not open source and it is likely for this reason alone that ET Pro will not ever be supported by ET:L. Even if they had permission to use the code they would have to scrap almost all of it - they have standards. hey the0ry, i've got an et:l question for you. et legacy does a great job of detecting and setting the best resolution when you first install it, but if it gets changed for some reason is there a way to re-do the auto detect that happens during install? i'm trying to get the resolution right with et:l on a new laptop and the usual commands make it crash. since i couldn't figure out a way to re-run the auto resolution detect that et:l does during install, i tried the old method of getting a custom resolution. i ran the following in the console: seta r_customwidth 1382 seta r_customheight 768 seta r_customaspect 1 seta r_mode -1 this produces a crash. i did a writeconfig before changing anything and i noticed that et:l lists r_mode as being "unsafe" and it is marked as such on the default et:l config. r_customaspect probably is as well. since these two cvars don't work with et:l, how can we manually enter a custom resolution in the console? edit: ok nvm! i went to put the error log up at pastebin and i noticed that the console lists the available modes before setting the custom resolution. 1382/768 is not supported, but 1366/768 is. i used 1366/768 instead and et:l doesn't crash. my resolution is fixed now. it would be cool if you could run the autodetect at any time in case you switch displays a lot. i'll have to mention it on their forum. i also noticed that the upside down cursor i was talking about earlier only appears after i play on an fa server. interesting. While in the Legacy mod and before connecting to a server you use the esc < options < system menu. There will be an auto feature available. Does more than stable 125fps help something too? I mean for example in COD4 125fps vs 250 were huge differents. With 250 stable fps it was much easyer to move and do some bounce and trickjumps The game will appear visually smoother. Most mods have fixed the rounding error that allowed you to jump higher. If your monitor runs a 60hz refresh rate you will run into more screen tearing, and you will be making your GPU work harder for little gain. Regards, Xeno 1 Quote
herpderp Posted March 12, 2014 Posted March 12, 2014 Does more than stable 125fps help something too? I mean for example in COD4 125fps vs 250 were huge differents. With 250 stable fps it was much easyer to move and do some bounce and trickjumps back in the day there were magic numbers that did help with movement. 43, 76, 125 and 333. this was all fixed years ago, so now its about matching monitor hz, fps and maxpackets Quote
staticwarp Posted March 13, 2014 Posted March 13, 2014 seriously, if you have fps issues in et, there's a bigger problem. i had 76-125 fps on a p4 years ago that being said, ill give this a look tomorrow. kinda curious about it what were the other specs on your pentium 4 pc (memory, gfx card, clock speed)? I have one and et doesn't run so well on it, i get like 26 fps even with medium settings. @xenozbad: cool, thanks! I didn't know about that, i will test it out. Quote
herpderp Posted March 13, 2014 Posted March 13, 2014 what were the other specs on your pentium 4 pc (memory, gfx card, clock speed)? I have one and et doesn't run so well on it, i get like 26 fps even with medium settings. @xenozbad: cool, thanks! I didn't know about that, i will test it out. at the time i had an x800 and 1 gig. you just need a low spec cfg and drop the res as low as is tollerable. you should be able to easily eek out 50-76 Quote
Arkinder Posted March 13, 2014 Posted March 13, 2014 what were the other specs on your pentium 4 pc (memory, gfx card, clock speed)? I have one and et doesn't run so well on it, i get like 26 fps even with medium settings. @xenozbad: cool, thanks! I didn't know about that, i will test it out. I wanted to clarify the location of the auto feature for ET:L. It is actually Esc < Options < Graphics < Set Recommended. With that being said not all of the features listed work out side of the Legacy mod but since you are using a lower end machine that is irrelevant. As for FPS issues there are several ways to improve your overall gaming experience. Windows settings, GPU settings, and lastly a config. If you would like some assistance feel free to PM me or make a post here. Regards, Xeno Quote
Dragonji Posted February 16, 2015 Posted February 16, 2015 (edited) etpro requires et260b, and checks if you have it. It's normal that it fails. It's perfectly possible to make a new ET compatible with etpro. I made it in a beta version of my demoviewer I never released, and in that custom ET to show hitboxes (the one we used in that old thread about etpro hitboxes here in this forum). It's up to them if they want to do it, but obviously it requires changes in etpro, and I maybe it would be a problem if they have to release the source code of that thing ET:L is an open source project, you are free to contribute and commit a code which will make it possible to play ETPro using ET:L client. https://github.com/etlegacy/etlegacy And if I run ET:L with rinput.exe the sensitivity is more than doubled, feels weird overall and some strange mouseaccel is there. They state on the website they will implement raw input in the next release, gonna try again then. For now there are no noticable improvements or bugfixes. A bunch of obsolete cvars are removed and Antialiasing can be enabled in the engine, but that's not worth a switch for me at least...ET:L uses raw input by default, there is no need to run ugly hacks for raw input. Installed and runs fine with Jaymod, but I have lower fps than with 2.6b. Settings are the same in ET and Nvidia driver for both games. demo1 150fps -> 140fps demo2 240fps -> 220fps The difference is too big. I'm sure you did not test both clients with same config. ET:L is a little bit slower at the moment but when I tested it myself I was only having 2-3% less FPS (on silEnT mod). Edited February 16, 2015 by Dragonji Quote
Scorpion_ Posted February 16, 2015 Posted February 16, 2015 You mean you have less FPS with ETl ? What's the point using it then...? Quote
Dragonji Posted February 16, 2015 Posted February 16, 2015 At the moment the main reasons are: - Better graphics (anisotropic filtering) - Working Alt-Tab minimizing - Less CPU load - Updated all libs directly used by ET (libjpeg replaced with libjpeg-turbo, curl etc) - Mouse raw input - Fixed security holes and exploits Read more here http://dev.etlegacy.com/projects/etlegacy/wiki/Changelog Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.