Last Month the Japanese try to retrive this mod a little bit more. They played in the at 2pm CET. At the moment the gametracker,com Server Monitorring is off. Hope soon they turn it on. The ranking seems to work.
Registered Member #640 Joined: [ 00:06 ] [ 03 Oct 2004 ] Posts: 16
Hi guys Im hoping someone can help me out.. I recently installed bf1942 with patches etc on my new computer running windows vista. The game worked perfect with no problems i then installed is82 and that works fine but now when i try and play bf1942 it crashes half way through the loading screen.Ive tried reinstalling them both but still no luck. any suggestions??
Shrooms
[ 22:02 ] [ 13 Nov 2008 ]
Guest
Where did you install it?
bf1942 patches needed: 1.6 1.61b
interstate patches needed 1.8 1.81
Did you try running in administrative mode? Tried running a singleplayer game?
Registered Member #78 Joined: [ 18:27 ] [ 13 Mar 2004 ]
RespecT wrote ...
The game worked perfect with no problems i then installed is82 and that works fine but now when i try and play bf1942 it crashes half way through the loading screen.Ive tried reinstalling them both but still no luck. any suggestions??
Did you try some of the modding tools? If so remove everything Interstate-related from your bf1942/init.con (open in notepad). Should be 2 lines there saying something about interstate.. Kill'em, and get back on the battlefield.
Registered Member #640 Joined: [ 00:06 ] [ 03 Oct 2004 ]
thanks for your help guys. ive checked the init.con and installed all the necessary patches, I also downloaded the mod again from another source and reinstalled but still no luck. gutz
Shrooms
[ 19:18 ] [ 14 Nov 2008 ]
Guest
check your bf1942 levels folder and see if you have accidentally placed a custom interstate map in it.
slick
[ 03:30 ] [ 15 Nov 2008 ]
Guest
ur probably running in XP compatability mode. xp mode causes bf42 to crash alot on map load. to fix this issue, right click ur bf1942 .exe, goto properties, go under the compatability tab, check the compatability mode checkbox, and set the compatability mode to windows NT. the older compatability mode will allow vista to run bf1942 using a much lower amount of system recources, without causing problems such as punkbuster issues or crackling sound in-game. this will allow maps to be loaded at a much faster rate, therefore preventing map crashes. i run in NT mode myself, and i nvr experience any map crashes, even on gutted @ max settings during map load. if the problem persists, tell me, and i'll look deeper
ignore the information below, the below has nothing to do with the is82 mod map crashes, unless u want to know why some mods, such as forgotten hope, battlegroup, or desert combat extended crash
Alex [ITA wrote ...
slick told me that (he has vista and...) you need to go to bf1942.exe properties and go compatibility thing and set Windows 95... well now i dunno if this is correct, ask him.
i've found alot more stuff since when i posted that, i later found out it wasn't the compatability mode that caused glitchy sound on 98 and 95 mode, but the inability to enable sound hardware acceleration. when ur in the menu, and goto options/sound, and 2nd menu, the hardware acceleration feature cannot be enabled due to directx10's loss of ability to enable directsound hardware acceleration. since directx10 is exclusive to vista, vista won't downgrade to directx9 even after uninstalling it through device manager and rebooting. it'll just reinstall itself since directx10 is a part of the vista os. if hardware acceleration could be enabled on vista, then the sound wouldn't be glitchy in 95 mode. 95 mode causes punkbuster server crashes nways
There is a problem with the version I have realised... when I do a fresh install of bf42 with all patches.... then install is82 with all patches... I find i cant join bf42 servers... because the version number is 1.6 and not 1.61...
does is82 1.81 rewrite the main bf1942 init to be v1.6 instead of 1.61?
Registered Member #78 Joined: [ 18:27 ] [ 13 Mar 2004 ]
Unless the installer itself alters registry-values, this is not the case. A fresh install leaves only an "Interstate" folder, nothing else. If you suspect this, try downloading the zipped version instead of using the installer. Link in Mac OSX interstate thread.