In both cases I was running 393 as client (as were other players).
In Scenario Phillipines, at start of the game the Indonesian sub Chakra was stuck at persicope depth (-10m) at its starting position (well at one of its alt start points). It would not dive even though the depth (in 393 client) showed -280m. However the depth at the exact same location in 3.9.4.9 showed to be -10m. Furthermore, as this was the start posit of the sub I know I placed the sub in deep water (using the 3.6 SE). Screenshot shows sub at -10m with Hermans enemy helo over it. Depth is -280m while herman saw depth at exactly same point to be -10m
I encountered this again in South Georgia, with a sub that started submerged in deep water but suddenly came to -10m appraoching the coast. Again in 393 client water depth showed -120m but in 3.9.4.9 it was obviously -10m. And again during scen design I checked that that position (a harbour) was deep enough for the sub in 36 SE.
This issue has now screwed up two MP sessions for me (one after 4 hours) and I regard is as major as all existing scens with subs are at risk. Issue can be replicated in MP and in Solitaire mode just by running the sub to the relevant positions. Therefore i do not believe its related to the use of 393 clients combined with 3949 server, but simply with the 3949 GE.
Of course this is also a specific example why in my opinion the Server should not be used with Beta's. The server was running Beta 3949 because in 3949 the Pause-bug of 393 is fixed, but this issue is more serious.
Freek
