I am now experiencing a crash to desktop that was never there before, after about an hours play the sodding thing just closes on me and Windows says there's been an error, sorry for the inconvenience. This was a fresh install to get rid of my mods and so forth, and the 1.3 patch put on top of that clean install. So now I have a game that crashes roughly every hour or so of play, and my sonarman is a deaf mute who doesn't report any contacts to me, yet draws a line on the map to them without saying.
Only a handful of the team being allowed to continue working on SH3, under enourmous pressure, whilst the rest are put onto something new (SH4? Ka-ching!). </div></BLOCKQUOTE>Originally posted by Kpt_Zig:
<BLOCKQUOTE class="ip-ubbcode-quote"><div class="ip-ubbcode-quote-title">quote:</div><div class="ip-ubbcode-quote-content">Originally posted by Feathered_IV:
Yes please, do explain what these conditions are........![]()
OH please! SH4
I make mistakes every day just like everyone else. But as we all know we have to acknowlage our mistakes, correct them, and move on.
SH3 patch 1.3 should be recalled and repaired. A simple ackowlagment on the main page would sufice, and we can all wait a few months more months for a good patch.
No harm, no fowl.![]()
For today's standards when a game lasts not more than a month or two, SH3 can be considered broken and the patches haven't fixed the CTDs. On the contrary they have now intoduced erratic cursor mouse movement and slow frame rates.Originally posted by Kpt_Zig:
Only a handful of the team being allowed to continue working on SH3, under enourmous pressure, whilst the rest are put onto something new (SH4? Ka-ching!).
Am not asking for new stuff like many people are (ships in ports or whatever); am only asking that they make the game playable by fixing CTDs (like the darn crew management button).
I don't blame the devs, I blame the top management.
There is no way I am buying SH4 even though SH3 is visualy stunning.
I'm wondering whether to install patch 1.3 or not - as far as I can see from the forums:
Pros
Corrected convoy protection
Corrected map (minor unless you live in Liverpool !) and can navigate straight from port
Better damage model
Diving depths updated
Improved nav tools
External camera linked to sub
View to heading and head to view (sounds very handy)
Torpedo tube ready notification by speech
(+ some other stuff)
Cons(most of which seem a bit inexplicable)
Sonar stops reporting contacts
No automatic pause when ship/plane spotted (even if on massive time compression)
Possibly a bit less stable
A few other (?minor things)
What I don't understand is that none of the cons seem related to what's actually been patched - Why have they been affected ???
It would be good to hear from the devs if there is a plan to sort out these problems soon - I like the sound of having fixed the convoy escort problem but not at the expense of a useful sonarman. And as I'm often not staring at the screen for hours at a time while my navigator gets the boat to the target area (I might go off to make a cup of tea for example) then not pausing if something major is happening is a bit of a disaster.
Can anyone tell me - do these problems affect everyone or is it just the unlucky few ?? (at least then I could try it and see what happened)
Thanks
Why in gods name forgott many people the UZO ?Originally posted by chrisoloughlin1:
I'm wondering whether to install patch 1.3 or not - as far as I can see from the forums:
Pros
Corrected convoy protection
Corrected map (minor unless you live in Liverpool !) and can navigate straight from port
Better damage model
Diving depths updated
Improved nav tools
External camera linked to sub
View to heading and head to view (sounds very handy)
Torpedo tube ready notification by speech
(+ some other stuff)
Cons(most of which seem a bit inexplicable)
Sonar stops reporting contacts
No automatic pause when ship/plane spotted (even if on massive time compression)
Possibly a bit less stable
A few other (?minor things)
What I don't understand is that none of the cons seem related to what's actually been patched - Why have they been affected ???
It would be good to hear from the devs if there is a plan to sort out these problems soon - I like the sound of having fixed the convoy escort problem but not at the expense of a useful sonarman. And as I'm often not staring at the screen for hours at a time while my navigator gets the boat to the target area (I might go off to make a cup of tea for example) then not pausing if something major is happening is a bit of a disaster.
Can anyone tell me - do these problems affect everyone or is it just the unlucky few ?? (at least then I could try it and see what happened)
Thanks
A very very importend thing is the UZO
The UZO at night is useless because of the Day light brightness in the UZO view.
You can see absolutly nothing with this thing at night and therefore its nearly impossible to make a surface attack.
What I don't understand is that none of the cons seem related to what's actually been patched - Why have they been affected ???
------------------------------------------------
This is a ****ed good question. I have a good deal of experience with coding myself. A complex program is normally broken down into specific subroutines that address and focus on a specific task. Sure they inter-react, but usually, you can perform surgery on one without a major impact on another. There will be a major descision making routine running in the background which will determine when and under what conditions these subroutines come into play. I suspect this is where something got fractured in v1.3
With regard to Zig's comment: "Only a handful of the team being allowed to continue working on SH3, under enourmous pressure, whilst the rest are put onto something new (SH4? Ka-ching!)."
I could have guessed this. I've worked for fortune 500 companies for 32 years. Standard operating proceedure. Considering the potential of this sim, it is very shortsighted, but hardly surprising. Those that are left in
developement are the "mop-up crew." They'll get a grip on it eventually, but we'll have to be patient.