Caution Press S in multiplayer 1.12a

[Fudd]

I have been getting press S after long loading times when playing online on HL. I have reinstalled 1.12a to ensure I am up to date. I have also changed the server config file to values equalling 600 for both.

 

I did notice that pingperiod = 1 was missing from the file... Is this a change in 1.12 or 1.12a and could this be causing me to get the press S message?

 

To note: I was playing on-line the morning before this happened, and I have been unable to play since that time due to I keep getting the press S message.

 

I first encountered the problem while on s77th server. I troubleshot as much as I could.

 

Ironhand, Goya and Konkussion maybe you can also input on what we tried that day to get it to work.

[Ironhand]

I have been getting press S after long loading times when playing online on HL...

 

Ironhand, Goya and Konkussion maybe you can also input on what we tried that day to get it to work.

First and very important, the problem first presented itself while you were trying to join through Hyperlobby. But it didn't only occur while using HL. The problem persisted when you connected directly through the sim's network interface as well. So it's probably not an HL problem per se.

 

IIRC, you also tried first restarting the sim before attempting to join. Also you rebooted your computer in case there was some temporary screwup that rebooting would fix.

 

Rich

[Fudd]

ED: Can you confirm that you have read this and do you have any suggestions?

[Gazehound]

Sometimes your config.lua gets screwed up when exiting a multiplayer session, resulting in the generation of a shorter file with half the info (this is based on observations with 1.11) If pingperiod = 1 is missing then maybe that is what is wrong - are there other omissions; eg the servers you have visited?

If so then it may be worth using someone elses config file (havent got it installed atm so I cant directly help you there).

[Fudd]

Thanks for the info Gazehound, I had no idea the config file could be modified in that way. WTF! :mad:

 

I will contact someone in my squad for a config.lua file, and I'll report back if that fixes the problem.

[S77th-Dante]

fudd, only caught you on comms for a sec tonight, but this is why this happens.

 

systems that are ..

 

cpu slow

low memory (less than 1024mb)

 

have Long Loading times.

 

during the Long Loading Time, the game sees you as 'inactive' and while you are loading you end up being timed out. this some how tricks the game into thinking you have to hit S to start like single player or hosting..

 

the end result is you either hit S, then it automaticly goes back to menu

or you hit S and you are not connected but still flying in the mission.

 

so moding the config is only an attempt to cover over the problem.

upgrading ram will most likely help and eliminate the problem compleatly.

[Gripes]

Sometimes your config.lua gets screwed up when exiting a multiplayer session, resulting in the generation of a shorter file with half the info (this is based on observations with 1.11) If pingperiod = 1 is missing then maybe that is what is wrong - are there other omissions; eg the servers you have visited?

If so then it may be worth using someone elses config file (havent got it installed atm so I cant directly help you there).

 

I`d better check my ".lua`s" then! I was on S77th server few days ago

and when I RTB`d (after letting some slammers loose) my pitch ladder got

pegged to the side of my HUD and some strong winds were pushing me

toward Turkey.

[Fudd]

fudd, only caught you on comms for a sec tonight, but this is why this happens.

 

systems that are ..

 

cpu slow

low memory (less than 1024mb)

 

have Long Loading times.

 

during the Long Loading Time, the game sees you as 'inactive' and while you are loading you end up being timed out. this some how tricks the game into thinking you have to hit S to start like single player or hosting..

 

the end result is you either hit S, then it automaticly goes back to menu

or you hit S and you are not connected but still flying in the mission.

 

so moding the config is only an attempt to cover over the problem.

upgrading ram will most likely help and eliminate the problem compleatly.

 

I have to disagree.

 

SO i went out last night and bought more memory. I am now up to 768mb, and with ending the programs in the background I have over 600mb for lock-on to play with.

 

After I upgraded I tried again entering a mission with only a couple of players in it. I again got the "press S" caution sign.

 

I then uninstalled lock-on, modman and used the starforce removal tool. I then defraged my C:\ drive and reinstalled the programs.

 

I then modified my config server.lua file to 600 for each time out.

 

I then joined a multiplayer game on 504th server, with no problems other than a long load time.

 

Who do i think the culprit is?

 

Could be starforce, could be a virus my system isn't catching... Lock-on has also been crashing after a fresh boot-up.

 

Everytime it crashes on the first load-up, I get "caution press s" in multiplayer on subsequent loadups

 

 

For right now things are fine, no crashes and no press s, I think I am just going to be plagued with frequent reinstallations :doh:

[S77th-Dante]

when i got 1.1 fc i had 512 ram. when connecting to servers i would get the S or loose connect.

 

at one stage 504th invited us (being the Savage 77th Squadron )to a game i wasnt able to get into the game at all after repeated attempts & reboots.

 

even with the modded file that had only braught some success.

 

i updated my ram 2 new sticks 1024mb '3200' and have not had the problem since. by the way when i did that starforce wanted a reactivation grrrrrrrrrrr.

 

after the upgrade i was running the game on high everything

later hard disk took a bleep (august) new hdd 'raptors' installed lock on ran like bleep can only run the game in 'low' now

[*Rage*]

I had the very same problem.....till i fixed it.

 

I changed the timeout settings in the config file but that didnt really help.

 

I think the problem is due to overly long load times that is compunded by the large multiplayer maps often used by the big HL servers (77th/504 and particularly 169th)

 

Since upgrading my very old (but reliable) hard drive to a newer faster one the problem has vanished.

 

I hope this helps.

[S77th-Dante]

just heard another story of a guy who was frustrated with the S to start who had 512mb ram.

 

he upgraded to 1024mb ram and the problem has be solved.

 

so if you have this problem there may be things that you can do to resolve it.