Ship Simulator

English forum => Ship Simulator Extremes => Topic started by: FREDMD2000 on March 17, 2011, 02:34:11

Title: 1.3.5 update and problems with SSE
Post by: FREDMD2000 on March 17, 2011, 02:34:11
I struggled with various problems after installing the update.  I had ships flying, lack of ability to get good resolution and a lot of other things.  For me the game was almost completely unplayable.  Performance problems for me seem have been resolved, but still couldn't really enjoy any sessions.  I finally bit the bullet and did a complete removal and re-installation.  It seems to have resolved most of the problems and I would recommend that anyone with ongoing problems do the same.  Question that I have for the forum members and VSTEP is, should the missions now be re-done using the latest update.  The reason i ask is that there still seems to be ongoing problems with both the missions provided by the original software as well as missions developed during the earlier versions (AI ships on suicide courses, airbourne ships etc) that still occur despite the upgrade.   Any feedback?  To me, it very frustrating to have a viable craft without the ability to use it well.  I am waiting for missions that appear to have been developed post 1.3.5 to see if they run any better.
Title: Re: 1.3.5 update and problems with SSE
Post by: Third Mate on March 17, 2011, 02:50:25
So first off did you buy the game from the store and you have STEAM and all of that or did you get it through ShipSim? When you applied the patch did you get it through STEAM or downloaded from the ShipSim website?
Title: Re: 1.3.5 update and problems with SSE
Post by: FREDMD2000 on March 17, 2011, 12:53:05
Non steam version purchased through amazon.  Downloaded the path from SS.
Title: Re: 1.3.5 update and problems with SSE
Post by: FREDMD2000 on March 17, 2011, 12:53:46
Patch not path
Title: Re: 1.3.5 update and problems with SSE
Post by: Third Mate on March 19, 2011, 08:43:53
Patch not path

Alright, next thing It would be good if you can post your dxDiag these problems sound all familiar, maybe I can get a better idea