Command and Conquer: Renegade Official Forums - RDF feed
C&C: Renegade --> Dying since 2003™, resurrected in 2024!
This time I got ALL the AGT problems. It will stop shooting you when the PP goes down or when its killed. And it will fire more than one missile. The reason there have been so many AGT problems this release is because, some time ago I wrote a clone of the AGT script (JFW_Advanced_Guard_Tower/JFW_Advanced_Guard_Tower_Gun/JFW_Advanced_Guard_Tower_Missile) and (unbeknownst to me) these scripts have been broken ever since they were written. It is a problem for 2.1 release because in 2.1 I added stuff to use my scripts instead of the stock westwood ones and also added code to help make the AGT missile/guns objects resistant to being killed by cheaters (like the PT fix that was done a while back) The AGT weapons do appear on Field in my own tests so any problems with that are not scripts.dll related. Also, I have confirmed that the DONATE command is working (in that I actually see calls to take money away and add money happening) so if that is broken, its also probobly not the scripts.dll get it from http://www.sourceforge.net/projects/rentools/ With any luck, this fixes all the 2.1 problems (and there wont be a 2.1.3)
You can also get an installer for scripts.dll 2.1.2 from http://www.4amdevlabs.com/scripts212setup.exe
God damn it DeadJonWil
Maybe I did something wrong but me and some others after installing them our renegades started to crash every 30 or so mins. Is it because these scripts are only for FDS's or what?
They work on Renegade Client perfectly. When it crashes, copy & paste your _except.txt to jonwil. he cannot resolve bugs if he doesn't know how they are caused
Thank you for that, But I do not have any file named "_except.txt"
its in your Renegade Directory (where game.exe is located)
Unfortunatly, I cant seem to match either of those trace dumps up to anything code wise.
*crys* well, tell me if i can provide you with any more information, for the time being i'm going back to 2.1.1
So 2.1.1 doesnt crash but 2.1.2 does? hmmm, there is one more thing you can do Go here: http://www.dependencywalker.com/ Download the latest version open game.exe go to "profile-start profiling" Clear all checkboxes. Click ok Play the game untill it crashes. Then, in depends.exe, down the bottom you should see something like Started "GAME2.EXE" (process 0x8C4) at address 0x00400000. then lines like Loaded "NTDLL.DLL" at address 0x7C900000. Post the whole bit from "Started game2.exe" down to Exited "GAME2.EXE". And also post the _except.txt from the crash. Also, post your operating system specs (e.g. Windows 98, Windows XP, Windows XP with Service Pack 2)
lol, i used 2.1.1 for 15 minutes b4, it didn't have a chance to crash... i found that it DOES crash, i have noticed one thing, the crashing versions of scripts comes with a bhs.dll which doubles in size, i'm gonna try to use the scripts 2.1.2 with the old BHS.DLL... i'll post resault in 20-30 min *fingers crossed* edit: downloaded "Dependency Walker 2.1"
ok, this is what the output was for the dependency walker: (the game never opened) i'm gonna run it with the ld BHS.dll now (well, gonna try) Started "GAME.EXE" (process 0xD64) at address 0x00400000. Loaded "NTDLL.DLL" at address 0x7C900000. Loaded "KERNEL32.DLL" at address 0x7C800000. Loaded "USER32.DLL" at address 0x77D40000. Loaded "GDI32.DLL" at address 0x77F10000. Loaded "SHELL32.DLL" at address 0x7C9C0000. Loaded "ADVAPI32.DLL" at address 0x77DD0000. Loaded "RPCRT4.DLL" at address 0x77E70000. Loaded "MSVCRT.DLL" at address 0x77C10000. Loaded "SHLWAPI.DLL" at address 0x77F60000. Entrypoint reached. All implicit modules have been loaded. Loaded "COMCTL32.DLL" at address 0x773D0000. Loaded "COMCTL32.DLL" at address 0x5D090000. Loaded "WS2_32.DLL" at address 0x71AB0000. Loaded "WS2HELP.DLL" at address 0x71AA0000. Second chance exception 0xC0000005 (Access Violation) occurred at address 0x00EB753D. Exited "GAME.EXE" (process 0xD64) with code -1073741819 (0xC0000005).
ok, so which operating system version do you have?
here it is (i have reason to beleave it's a acces violation with RG because i played without RG for more than 45 minutes now and it hasn't crashed!) Started "GAME2.EXE" (process 0xCE4) at address 0x00400000. Loaded "NTDLL.DLL" at address 0x7C900000. Loaded "KERNEL32.DLL" at address 0x7C800000. Loaded "MSS32.DLL" at address 0x21100000. Loaded "USER32.DLL" at address 0x77D40000. Loaded "GDI32.DLL" at address 0x77F10000. Loaded "WINMM.DLL" at address 0x76B40000. Loaded "ADVAPI32.DLL" at address 0x77DD0000. Loaded "RPCRT4.DLL" at address 0x77E70000. Loaded "OLE32.DLL" at address 0x774E0000. Loaded "MSVCRT.DLL" at address 0x77C10000. Loaded "AVIFIL32.DLL" at address 0x73B50000. Loaded "MSACM32.DLL" at address 0x77BE0000. Loaded "MSVFW32.DLL" at address 0x75A70000. Loaded "SHELL32.DLL" at address 0x7C9C0000. Loaded "SHLWAPI.DLL" at address 0x77F60000. Loaded "COMCTL32.DLL" at address 0x5D090000. Loaded "WSOCK32.DLL" at address 0x71AD0000. Loaded "WS2_32.DLL" at address 0x71AB0000. Loaded "WS2HELP.DLL" at address 0x71AA0000. Loaded "VERSION.DLL" at address 0x77C00000. Loaded "BINKW32.DLL" at address 0x30000000. Loaded "BANDTEST.DLL" at address 0x10000000. Loaded "IMM32.DLL" at address 0x76390000. Entrypoint reached. All implicit modules have been loaded. Loaded "COMCTL32.DLL" at address 0x773D0000. Loaded "MSCTF.DLL" at address 0x74720000. Loaded "MSGPLUSLOADER1.DLL" at address 0x00E30000. Loaded "MP3DEC.ASI" at address 0x26F00000. Loaded "MSSA3D.M3D" at address 0x22100000. Loaded "MSSDS3DH.M3D" at address 0x22400000. Loaded "MSSEAX.M3D" at address 0x22500000. Loaded "MSSEAX2.M3D" at address 0x22C00000. Loaded "MSSDOLBY.M3D" at address 0x22700000. Loaded "MSSFAST.M3D" at address 0x22600000. Loaded "DSOUND.DLL" at address 0x73F10000. Loaded "WDMAUD.DRV" at address 0x72D20000. Loaded "SETUPAPI.DLL" at address 0x77920000. Loaded "WINTRUST.DLL" at address 0x76C30000. Loaded "CRYPT32.DLL" at address 0x77A80000. Loaded "MSASN1.DLL" at address 0x77B20000. Loaded "IMAGEHLP.DLL" at address 0x76C90000. Unloaded "SETUPAPI.DLL" at address 0x77920000. Loaded "MSACM32.DRV" at address 0x72D10000. Loaded "MIDIMAP.DLL" at address 0x77BD0000. Loaded "SETUPAPI.DLL" at address 0x77920000. Unloaded "SETUPAPI.DLL" at address 0x77920000. Loaded "SETUPAPI.DLL" at address 0x77920000. Unloaded "SETUPAPI.DLL" at address 0x77920000. Loaded "SETUPAPI.DLL" at address 0x77920000. Unloaded "SETUPAPI.DLL" at address 0x77920000. Loaded "SETUPAPI.DLL" at address 0x77920000. Unloaded "SETUPAPI.DLL" at address 0x77920000. Loaded "KSUSER.DLL" at address 0x73EE0000. Loaded "SETUPAPI.DLL" at address 0x77920000. Unloaded "SETUPAPI.DLL" at address 0x77920000. Loaded "SETUPAPI.DLL" at address 0x77920000. Unloaded "SETUPAPI.DLL" at address 0x77920000. Loaded "SETUPAPI.DLL" at address 0x77920000. Unloaded "SETUPAPI.DLL" at address 0x77920000. Loaded "D3D8.DLL" at address 0x6D9A0000. Loaded "D3D8THK.DLL" at address 0x6D990000. Loaded "DINPUT8.DLL" at address 0x6CE10000. Loaded "HID.DLL" at address 0x688F0000. Loaded "SETUPAPI.DLL" at address 0x77920000. Loaded "SCRIPTS.DLL" at address 0x06DA0000. Loaded "BHS.DLL" at address 0x06E60000. Loaded "SCRIPTS2.DLL" at address 0x06EA0000. Loaded "MSWSOCK.DLL" at address 0x71A50000. Loaded "DNSAPI.DLL" at address 0x76F20000. Loaded "WINRNR.DLL" at address 0x76FB0000. Loaded "WLDAP32.DLL" at address 0x76F60000. Loaded "RASADHLP.DLL" at address 0x76FC0000. Loaded "MSLBUI.DLL" at address 0x605D0000. Loaded "CLBCATQ.DLL" at address 0x76FD0000. Loaded "OLEAUT32.DLL" at address 0x77120000. Loaded "COMRES.DLL" at address 0x77050000. Loaded "WOLAPI.DLL" at address 0x21000000. Loaded "SNMPAPI.DLL" at address 0x71F60000. Loaded "HNETCFG.DLL" at address 0x662B0000. Loaded "WSHTCPIP.DLL" at address 0x71A90000. Loaded "ICMP.DLL" at address 0x74290000. Loaded "IPHLPAPI.DLL" at address 0x76D60000. Unloaded "ICMP.DLL" at address 0x74290000. Loaded "INETMIB1.DLL" at address 0x666F0000. Loaded "MPRAPI.DLL" at address 0x76D40000. Loaded "ACTIVEDS.DLL" at address 0x77CC0000. Loaded "ADSLDPC.DLL" at address 0x76E10000. Loaded "NETAPI32.DLL" at address 0x5B860000. Loaded "ATL.DLL" at address 0x76B20000. Loaded "RTUTILS.DLL" at address 0x76E80000. Loaded "SAMLIB.DLL" at address 0x71BF0000. Unloaded "INETMIB1.DLL" at address 0x666F0000. Unloaded "SCRIPTS.DLL" at address 0x06DA0000. Unloaded "SCRIPTS2.DLL" at address 0x06EA0000. Loaded "QQHOOK.DLL" at address 0x06DA0000. Loaded "SECUR32.DLL" at address 0x77FE0000. Unloaded "MP3DEC.ASI" at address 0x26F00000. Unloaded "MSSA3D.M3D" at address 0x22100000. Unloaded "MSSDS3DH.M3D" at address 0x22400000. Unloaded "MSSEAX.M3D" at address 0x22500000. Unloaded "MSSEAX2.M3D" at address 0x22C00000. Unloaded "MSSDOLBY.M3D" at address 0x22700000. Unloaded "MSSFAST.M3D" at address 0x22600000. Unloaded "DINPUT8.DLL" at address 0x6CE10000. Unloaded "HID.DLL" at address 0x688F0000. Unloaded "D3D8.DLL" at address 0x6D9A0000. Unloaded "D3D8THK.DLL" at address 0x6D990000. Unloaded "WOLAPI.DLL" at address 0x21000000. Unloaded "SNMPAPI.DLL" at address 0x71F60000. Exited "GAME2.EXE" (process 0xCE4) with code 0 (0x0). added* Win XP SP2 with latest updates edit: forthur more, i technicly --can-- unpack/unencript RG for this testing but then i'll get banned or something (-_-)
Show me the _except.txt that matches with the crash you just showed me
Quote: hasn't crashed!) ok heres what i think, cos i ran it with the 2.1.2 scripts and the old BHS.dll == NO CRASH These things i've tryed: new bhs.dl + new scripts + RG = fast load + crash new bhs.dl + new scripts (not running rg) + depends.exe (not shore if depends.exe makes a difference)= fast load (no crash, tested for 45min) old BHS.dll + new scripts = normal load (no crash, tested for 1 hour) old BHS + old scripts = normal load (no crash)
although there is a possibility... but it's not possible that RG causes crash on itself, it something to do with BHS.dll and RG's interaction (well, i think)
RG doesn't interact with BHS.dll. It's probably just some crappy coding causing the problem.
dosn't RG even check BHS.DLL for modifications???
Open bhs.dll in your text editor
Veryfing a file on your harddrive and running program using this file do not relate.
we haved use the newest bhs.dll on a clanserver all members with the newest one (bhs.dll from scripts2.1) get kicked @same time , all have the same errormessage , 6 peps chrased on same time , all on another pc configiration , there must be a major bug in bhs.dll
Well, dont hold your breath if your looking for an answer here. I come here evryday looking for a fix, and your post is the first one I have seen in nearly 2 weeks.
You cannot use a scripts 2.0-based SSAOW (which it currently it is) with a scripts2.1-based bhs.dll. This will cause problems. You may only use a scripts 2.1-based bhs.dll with a scripts 2.1-based scripts.dll on your server and client
I am getting reports of crashes in 2.1.2 from a few people but I cant actually link the crash logs back to the faulty code. So I have no idea what might be causing the crashes
I used the scripts.dll and bhs.dll 2.1.2 from SF and my game crashed several times. So I did an uninstall and reinstalled game/1.037/djlaptop_cd_crack/rengaurd/cp1 and it worked fine. Thinking I made a mistake I used the utility provided under this same topic to install 2.1.2 and it crashed. I did the aforementioned uninstall reinstall and used the 2.1.1 utility to see if it crashed, and it did crash. I waited around for an answer and saw no progress so I decided to try it again. This time I only changed the scripts and bhs from 2.1.2 with the ones in the renegade file, and it crashed. I took the new scripts back out put the old one back in, and it crashed. I put the new scripts back in and took the old one out, then took the new bhs out and put the old one back in and it hasn't crashed so far. Damn, now I'm confused. So in summery it is game/1.037/djlaptop_cd_crack/rengaurd/cp1/scripts 2.1.2/bhs.dll (I asume this is from cp1) 60.5 KB (61,952 bytes) I really like the client log that bhs has so any help would be appreciated. BTW I have this I have this from 1 of my logs that says a mod is using big head. Is this true or is it a smart ass comment from BRenBot? [19:34] Host: mean50 is a protected nickname. Please authenticate yourself within 60 seconds, or you will be kicked. [19:34] Host: mean50 is a protected nickname. Please authenticate yourself within 60 seconds, or you will be kicked. [19:34] Host: mean50 is a game moderator. [19:34] Host: [BR] [mean50] is running Big Head. [19:34] Host: mean50 is a game moderator. [19:34] Host: [BR] [mean50] is running Big Head. [19:34] Host: [BR] Shotgun, flamethrower, sniper rifle, mean50 is a master of them all, less the sleep -- it gets in the way of renegade! (292 recommendations) [19:34] Host: [BR] mean50 knows, in the end there is only Renegade. (292 recommendations) [19:34] Host: [BR] Wow playing with portonew is almost better then having sex, almost! (4 recommendations) [19:34] Host: [BR] Server Rules: We will not tolerate any cheats of any kind. No base 2 base. no buddy jumping and no Grand Theft Auto. [19:35] [Team] mision08: stupid sbh Thanks, baby arm
!setjoin is running Big Head.
jonwil I am getting reports of crashes in 2.1.2 from a few people but I cant actually link the crash logs back to the faulty code. So I have no idea what might be causing the crashes hhaahahah, this is funnies.
I'm not sure but I think the problem is with a windows security feature. while I was posting the previous rant I right clicked on scripts.dll to get the size. At the bottom of properties it had an unblock button. I unblocked scripts, then put bhs.dll back into my renegade folder and did the same. So far so good. "!setjoin is running big head" I don't get it. What is this you speak of?
You can set a message, that will be displayer when you join the server with !setjoin
Oh, I see said the blind man. I appreciate your knowledge and wisdom. I went back to the original bhs.dll with the new scripte.dll from the 2.1.2 Is this a bad combination? I read that the windows XP service pac 2 has caused a lot of problems with some applications. I personally have this OS configuration. Is this a common theme with the users that have problems with the new bhs.dll?