|
|
#16 |
![]() Join Date: Sep 2007
Reputation: 19
Posts: 559
|
|
|
|
|
|
|
#17 | |
|
Guest
Posts: n/a
|
Quote:
|
|
|
|
|
#18 | |
|
Guest
Posts: n/a
|
Quote:
Well i am still on Version 1.0.0.0 After so long apprently this should upgrade automatically and guess what its not happend. Soo jarateed off And got no reply to the Letter i sent either
|
|
|
|
|
#19 |
![]() Join Date: Jun 2009
Reputation: 6
Posts: 27
|
Gentlemen,
The issue is one which Steam is going to have to address, but is largely due to a programming mis-step by VSTEP (pun intended) in the programming of this application. Basically, there are several "add-ons" for Ship Sim Extremes, and several patches. The problem is that the "add-ons" over-write significant chunks of the application, which causes it to be detected as an older version. Basically, if dealing with a boxed set, here's the sequence of installation which I've found works: 1) Clean-install of the program. (version 1.0.0) 2) Install "Fishing Trawler SIGITIA" DLC (which installs some application files which cause the program to read as v1.1.0). 3) Install update 1.3.5 4) Install the "Ferry Add-on Pack." (which installs some application files which cause the program to read as 1.3.5) 5) Install update 1.4.0. 6) Install CCC Winner and CCC Deniz Doga DLC packages (which require program version 1.4.0, and likely also install some application files which will cause the program to read as 1.4.0 later on). I had HORRIBLE problems with this... because I assumed, LOGICALLY, that DLC would not overwrite program files. Bad assumption. I'd install the program, the 1.3.5 "full update" and the 1.4.0 "incremental update," then install Sigita, and the program would show that it was v1.1.0 again (even though the main executable remained at v1.4.0). If I skipped Sigita, and installed the Ferry Pack, it would have been backstepped to 1.3.5 (even though the main executable wasn't changed, again). Also, I found that if I ever ran the program before getting all the subcomponents installed, something would get recorded someplace (in the registry? In the user documents folder? I don't know!) which would cause problems later on. So... all of those steps, above, had to be done IN SEQUENCE, before ever running the program. Oh, yes, and there's also a little bug with detection of certain more recent nVidia drivers... where the program would seemingly not be able to find the driver, and would thus default to a very low resolution (from which I would be unable to switch). By running driver 266.58, I'm able to get it work, but not with the more recent drivers (288.xx, 290.xx, etc). The program itself is pretty fun, if you're so inclined, but there are some places in the programming where the programmers absolutely "outsmarted themselves" and have caused problems. Now... STEAM is responsible for getting the installation scheme right for STEAM users. Clearly, they never really bothered to do so. So, if you're a STEAM purchaser of this program, your complaints should be targetted at STEAM, not at VSTEP... even though it's VSTEP's programming SNAFUs which cause this problem. STEAM is making money from you by selling you a "delivery system" which is supposed to be seamless and transparent to the user. In this case, they've failed utterly. But I was able to figure this out, without too much of a headache... and I'm not getting paid to do so. STEAM, who are getting PAID BY YOU to provide that service, are obligated, legally, to do so. |
|
|
|
![]() |
|
||||||
| Thread Tools | |
| Display Modes | |
|
|