Base Time 2018

[Front Runner]

I did a bit of research on 30 FPS games and found that UBIsoft actually recommends setting many of “their” games to 30 FPS..
Here is a link to UBIsoft customer support post about FPS. Interesting.
https://support.ubi.com/en-US/faqs/000031917

Also, here is a discussion about adaptive v-sync and 1/2 refresh rate.

https://steamcommunity.com/app/23467...448/?l=turkish

I’m finding that SH4 runs very smoothly using adaptive v-sync and 1/2 refresh rate. I’m getting 30fps and very few “micro-pauses”.
I’m not having any noticeable “input lag.”
These settings, so far, nearly eliminate the “No V-sync, “balls out FPS” synchronization error that I previously reported.
I’m well into my third day underway at 1x play and my last sunrise was off by only 2 minutes! I believe that SH4 runs best, all around, at 30 fps.
I’m now wondering if the synchronization error also applies to SH3!

[KaleunMarco]

Originally Posted by Front Runner

I did a bit of research on 30 FPS games and found that UBIsoft actually recommends setting many of “their” games to 30 FPS..
Here is a link to UBIsoft customer support post about FPS. Interesting.
https://support.ubi.com/en-US/faqs/000031917

Also, here is a discussion about adaptive v-sync and 1/2 refresh rate.

https://steamcommunity.com/app/23467...448/?l=turkish

I’m finding that SH4 runs very smoothly using adaptive v-sync and 1/2 refresh rate. I’m getting 30fps and very few “micro-pauses”.
I’m not having any noticeable “input lag.”
These settings, so far, nearly eliminate the “No V-sync, “balls out FPS” synchronization error that I previously reported.
I’m well into my third day underway at 1x play and my last sunrise was off by only 2 minutes! I believe that SH4 runs best, all around, at 30 fps.
I’m now wondering if the synchronization error also applies to SH3!

great research, gents.


how does a dumb-user change their (there for propbeanie) refresh rate to 30?

[propbeanie]

If you have an nVidia card, the Steam link in Front Runner's post is the one to follow:

https://steamcommunity.com/app/23467...448/?l=turkish

You open the nVidia control panel and do what the guy has in his imgur picture. If you're like me, and have multiple installs of Silent Hunter for various mods, then it's best to use the "Add" and "Browse" buttons to be sure you are using the correct SH4.exe file. Only the two settings for "Vertical Sync (Adaptive - half refresh rate)" and "Maximum Pre-Rendered Frames (2)". The game does look a ~lot~ smoother on my quad-core with the 560. I have not done much other than play the game. I'll try to do my Single Mission from the Amazon River mouth towards Greenland at 1x TC all day today and night, and see what it does as far as the celestial cycles.

The laptop I have has Intel HD graphics, and does not have any control over the frame rate or buffering at all. I no longer have an ATI / AMD card installed in my computers (well, an AIW 9600XT in the XP box for vid cap), so I don't remember if there's any user-definable settings for 3D or not... profiles maybe, for individual games??

[Front Runner]

Originally Posted by propbeanie

If you have an nVidia card, the Steam link in Front Runner's post is the one to follow:

https://steamcommunity.com/app/23467...448/?l=turkish

You open the nVidia control panel and do what the guy has in his imgur picture. If you're like me, and have multiple installs of Silent Hunter for various mods, then it's best to use the "Add" and "Browse" buttons to be sure you are using the correct SH4.exe file. Only the two settings for "Vertical Sync (Adaptive - half refresh rate)" and "Maximum Pre-Rendered Frames (2)". The game does look a ~lot~ smoother on my quad-core with the 560. I have not done much other than play the game. I'll try to do my Single Mission from the Amazon River mouth towards Greenland at 1x TC all day today and night, and see what it does as far as the celestial cycles.

The laptop I have has Intel HD graphics, and does not have any control over the frame rate or buffering at all. I no longer have an ATI / AMD card installed in my computers (well, an AIW 9600XT in the XP box for vid cap), so I don't remember if there's any user-definable settings for 3D or not... profiles maybe, for individual games??

Have you tried using nVidia Inspector? It gives additional options to control settings over and above the simple nVidia Control Panel, and allows you to set up a profile and than add all the executables that you wish to run under that profile's settings.


https://www.guru3d.com/files-details...-download.html


Here is the guide on how to use it. This link also contains the link to download the most current version from Guru3D


https://forums.guru3d.com/threads/nv...-guide.403676/

[propbeanie]

Them fellers are into that kind of stuff big-time. Makes it easier for us, eh?

[Front Runner]

Originally Posted by propbeanie

Them fellers are into that kind of stuff big-time. Makes it easier for us, eh?

Here is another TWEAK GUIDE for nVidia GPUs. It explains each setting and why/why not.


http://www.tweakguides.com/NVFORCE_1.html

[KaleunMarco]

Originally Posted by propbeanie

Them fellers are into that kind of stuff big-time. Makes it easier for us, eh?

yes, they are. don't give a hoot about frame rates. BUT (notice the big but) i think it is perfectly fine if others want to pursue that aspect of the game.

[Front Runner]

Originally Posted by propbeanie

Them fellers are into that kind of stuff big-time. Makes it easier for us, eh?

I just discovered a BIGGY. I'm not sure if this has ever been isolated or reported before.
It happened like this. I was starting up SH4 FOTRSUv80 RS2 this morning and I loaded up the save game that I saved last night. As sometimes happens, the RADIO is already playing when the scene opens in the control room. Other than that, nothing seems out of whack. Normally, I would either back out to the Main Menu, or back out to Windows and try again.

This time, I decided to try, as I sometimes do, loading an earlier save. I did, and when the scene opened in the control room the RADIO was NOT playing. OK, good, now I'll load up the save game where I left off last night.
One save game was made right at SUNSET. The other save game was a NOON save game. I am playing at a combination of 1x and 512x time compression.

NOW, here is the discovery. When I loaded up the NOON save game and it opened to the Control Room scene and the RADIO was off, I immediately loaded up the SUNSET save game and when it loaded, I started playing from the MAP (F5) and set TC at 512x. Shortly thereafter I get a RADAR CONTACT. So I order a Crash Dive and then go to external view. That is when I noticed that it was broad daylight! I mean like NOON broad daylight.
OK, when I had loaded up the SUNSET save game (the second time), and it started, I neglected to notice that, one, the lighting in the control room was daytime, and, the lighting on the MAP was also daytime.

What I had inadvertently discovered is the source of the very whacked out Base Time differentials. Propbeanie, I remember you mentioning this before that you also noticed some Base Time shifts when loading and/or reloading previous save games.


Had I continued to play, Base Time would've lost ALL meaning because, by loading the NOON save game, then upon opening the control room scene and immediately loading the SUNSET save, (and not noticing that Base Time vs Celestial Sphere was WAY out of whack,) then ALL of my subsequent save games would've been based on the whacked out Base Time vs Celestial Sphere.


I was able to repeat this several times and every single time, the error occurred. I have the save games that I used in case you are interested in trying, but I think you can test this yourselves by,


1. Starting SH4 and loading a save game that you know was made near SUNSET or at NIGHT. Notice that the CONTROL ROOM lights are red. (Night)
Note your Base Time. (Mine was 2036 which was correct according to my Lat. Long position referenced to my Midway Base.)


2. When the (Step 1) CONTROL ROOM scene opens, before you do anything else, load a save game that you know was made near NOON or during DAYLIGHT hours. Notice that the CONTROL ROOM lights are white. (Daylight) Note your Base Time. (Mine was 1215 which was NOON at my Midway Base.)
I don't care what my local noon is/was. That Base Time is where I make my save games when playing. For example, I make saves at SR, SS, NOON, MR, MS, and MIDNIGHT.


3. When the (Step 2) CONTROL ROOM scene opens, before you do anything else, load the save game from Step 1. When the CONTROL ROOM scene opens, the CONTROL ROOM lights are still white. (Daylight) Note your Base Time. (Mine was 2036 just as it was in Step 1.)



4. Go to external view and see the sun high in the sky even though your Base Time is indicating sunset or night time (for you.)


Now, I tried to correct the error by backing out to the MAIN menu and again loading my Sunset Save. Nope, that didn't get ride of the Celestial Sphere displacement caused by the above steps.
Then, I closed SH4 to Windows. I did not restart the computer nor did I log out of being the current user. I restarted SH4 and reloaded my SUNSET save and all was right with the world. My Base Time was correct and my Celestial Sphere was in sync with my save game.


I hope that you have all been able to follow this. If you have, then you can begin to see the implications and how it absolutely affects game play.
If I had continued on my Patrol without restarting SH4, my combined Celestial Sphere displacement caused by Steps 1 -4 above, and, the typical (and CORRECT) Base Time displacement from Midway, would've made it completely and utterly impossible to calculate Base Time and know whether it is DAY or NIGHT for the ENEMY. Nor would I be able to predict SR, SS, MR, or MS.



I was able to duplicate this error several times before I decided to post my observations.


Propbeanie, this explains your observations. I don't believe this is a FOTRSUv80 RS2 issue. I believe that it is a VANILLA Game issue. I'll try to verify this soon.



All because of the RADIO playing on LOAD game, which happens from time to time.

[propbeanie]

Originally Posted by Front Runner

I just discovered a BIGGY. I'm not sure if this has ever been isolated or reported before.
It happened like this. I was starting up SH4 FOTRSUv80 RS2 this morning and I loaded up the save game that I saved last night. As sometimes happens, the RADIO is already playing when the scene opens in the control room. Other than that, nothing seems out of whack. Normally, I would either back out to the Main Menu, or back out to Windows and try again.

This time, I decided to try, as I sometimes do, loading an earlier save. I did, and when the scene opened in the control room the RADIO was NOT playing. OK, good, now I'll load up the save game where I left off last night.
One save game was made right at SUNSET. The other save game was a NOON save game. I am playing at a combination of 1x and 512x time compression.

NOW, here is the discovery. When I loaded up the NOON save game and it opened to the Control Room scene and the RADIO was off, I immediately loaded up the SUNSET save game and when it loaded, I started playing from the MAP (F5) and set TC at 512x. Shortly thereafter I get a RADAR CONTACT. So I order a Crash Dive and then go to external view. That is when I noticed that it was broad daylight! I mean like NOON broad daylight.
OK, when I had loaded up the SUNSET save game (the second time), and it started, I neglected to notice that, one, the lighting in the control room was daytime, and, the lighting on the MAP was also daytime.

What I had inadvertently discovered is the source of the very whacked out Base Time differentials. Propbeanie, I remember you mentioning this before that you also noticed some Base Time shifts when loading and/or reloading previous save games.


Had I continued to play, Base Time would've lost ALL meaning because, by loading the NOON save game, then upon opening the control room scene and immediately loading the SUNSET save, (and not noticing that Base Time vs Celestial Sphere was WAY out of whack,) then ALL of my subsequent save games would've been based on the whacked out Base Time vs Celestial Sphere.


I was able to repeat this several times and every single time, the error occurred. I have the save games that I used in case you are interested in trying, but I think you can test this yourselves by,


1. Starting SH4 and loading a save game that you know was made near SUNSET or at NIGHT. Notice that the CONTROL ROOM lights are red. (Night)
Note your Base Time. (Mine was 2036 which was correct according to my Lat. Long position referenced to my Midway Base.)


2. When the (Step 1) CONTROL ROOM scene opens, before you do anything else, load a save game that you know was made near NOON or during DAYLIGHT hours. Notice that the CONTROL ROOM lights are white. (Daylight) Note your Base Time. (Mine was 1215 which was NOON at my Midway Base.)
I don't care what my local noon is/was. That Base Time is where I make my save games when playing. For example, I make saves at SR, SS, NOON, MR, MS, and MIDNIGHT.


3. When the (Step 2) CONTROL ROOM scene opens, before you do anything else, load the save game from Step 1. When the CONTROL ROOM scene opens, the CONTROL ROOM lights are still white. (Daylight) Note your Base Time. (Mine was 2036 just as it was in Step 1.)



4. Go to external view and see the sun high in the sky even though your Base Time is indicating sunset or night time (for you.)


Now, I tried to correct the error by backing out to the MAIN menu and again loading my Sunset Save. Nope, that didn't get ride of the Celestial Sphere displacement caused by the above steps.
Then, I closed SH4 to Windows. I did not restart the computer nor did I log out of being the current user. I restarted SH4 and reloaded my SUNSET save and all was right with the world. My Base Time was correct and my Celestial Sphere was in sync with my save game.


I hope that you have all been able to follow this. If you have, then you can begin to see the implications and how it absolutely affects game play.
If I had continued on my Patrol without restarting SH4, my combined Celestial Sphere displacement caused by Steps 1 -4 above, and, the typical (and CORRECT) Base Time displacement from Midway, would've made it completely and utterly impossible to calculate Base Time and know whether it is DAY or NIGHT for the ENEMY. Nor would I be able to predict SR, SS, MR, or MS.



I was able to duplicate this error several times before I decided to post my observations.


Propbeanie, this explains your observations. I don't believe this is a FOTRSUv80 RS2 issue. I believe that it is a VANILLA Game issue. I'll try to verify this soon.



All because of the RADIO playing on LOAD game, which happens from time to time.

That can happen with or without anything else going on, from what I remember. I've encountered that before without opening a 2nd Save. The game just gets confused sometimes. Thankfully, not real often. You especially have to be careful with add-in radio & grammafone mods. There is a little "mod" app to check them... now, where did I have that?...

If you want to try this - copy your Save folder before you do though - but do like you did with Step 1, Step 2, & Step 3, but Save sometime after Step 3, and that Save is borked* for the duration. Your clock will be off until you end patrol. Talk about messing with your head. "Let's see, it's 2230, nothing on sonar. I should be safe to surface. 'Surface the boat' - 'Incoming aircraft!' - 'We're under attack, sir!' Boom! Boom! 'We're taking damage, Sir!' - 'Medic!'"...

* For you youngsters, look up Robert Bork...

[KaleunMarco]

Originally Posted by Front Runner

I just discovered a BIGGY. I'm not sure if this has ever been isolated or reported before.
It happened like this. I was starting up SH4 FOTRSUv80 RS2 this morning and I loaded up the save game that I saved last night. As sometimes happens, the RADIO is already playing when the scene opens in the control room. Other than that, nothing seems out of whack. Normally, I would either back out to the Main Menu, or back out to Windows and try again.

This time, I decided to try, as I sometimes do, loading an earlier save. I did, and when the scene opened in the control room the RADIO was NOT playing. OK, good, now I'll load up the save game where I left off last night.
One save game was made right at SUNSET. The other save game was a NOON save game. I am playing at a combination of 1x and 512x time compression.

NOW, here is the discovery. When I loaded up the NOON save game and it opened to the Control Room scene and the RADIO was off, I immediately loaded up the SUNSET save game and when it loaded, I started playing from the MAP (F5) and set TC at 512x. Shortly thereafter I get a RADAR CONTACT. So I order a Crash Dive and then go to external view. That is when I noticed that it was broad daylight! I mean like NOON broad daylight.
OK, when I had loaded up the SUNSET save game (the second time), and it started, I neglected to notice that, one, the lighting in the control room was daytime, and, the lighting on the MAP was also daytime.

What I had inadvertently discovered is the source of the very whacked out Base Time differentials. Propbeanie, I remember you mentioning this before that you also noticed some Base Time shifts when loading and/or reloading previous save games.


Had I continued to play, Base Time would've lost ALL meaning because, by loading the NOON save game, then upon opening the control room scene and immediately loading the SUNSET save, (and not noticing that Base Time vs Celestial Sphere was WAY out of whack,) then ALL of my subsequent save games would've been based on the whacked out Base Time vs Celestial Sphere.


I was able to repeat this several times and every single time, the error occurred. I have the save games that I used in case you are interested in trying, but I think you can test this yourselves by,


1. Starting SH4 and loading a save game that you know was made near SUNSET or at NIGHT. Notice that the CONTROL ROOM lights are red. (Night)
Note your Base Time. (Mine was 2036 which was correct according to my Lat. Long position referenced to my Midway Base.)


2. When the (Step 1) CONTROL ROOM scene opens, before you do anything else, load a save game that you know was made near NOON or during DAYLIGHT hours. Notice that the CONTROL ROOM lights are white. (Daylight) Note your Base Time. (Mine was 1215 which was NOON at my Midway Base.)
I don't care what my local noon is/was. That Base Time is where I make my save games when playing. For example, I make saves at SR, SS, NOON, MR, MS, and MIDNIGHT.


3. When the (Step 2) CONTROL ROOM scene opens, before you do anything else, load the save game from Step 1. When the CONTROL ROOM scene opens, the CONTROL ROOM lights are still white. (Daylight) Note your Base Time. (Mine was 2036 just as it was in Step 1.)



4. Go to external view and see the sun high in the sky even though your Base Time is indicating sunset or night time (for you.)


Now, I tried to correct the error by backing out to the MAIN menu and again loading my Sunset Save. Nope, that didn't get ride of the Celestial Sphere displacement caused by the above steps.
Then, I closed SH4 to Windows. I did not restart the computer nor did I log out of being the current user. I restarted SH4 and reloaded my SUNSET save and all was right with the world. My Base Time was correct and my Celestial Sphere was in sync with my save game.


I hope that you have all been able to follow this. If you have, then you can begin to see the implications and how it absolutely affects game play.
If I had continued on my Patrol without restarting SH4, my combined Celestial Sphere displacement caused by Steps 1 -4 above, and, the typical (and CORRECT) Base Time displacement from Midway, would've made it completely and utterly impossible to calculate Base Time and know whether it is DAY or NIGHT for the ENEMY. Nor would I be able to predict SR, SS, MR, or MS.



I was able to duplicate this error several times before I decided to post my observations.


Propbeanie, this explains your observations. I don't believe this is a FOTRSUv80 RS2 issue. I believe that it is a VANILLA Game issue. I'll try to verify this soon.



All because of the RADIO playing on LOAD game, which happens from time to time.

Runner...
so you are saying that, under certain circumstances, the main application will carryover celestial time from one game instance to another? so the ubisoft programmers forgot to reset game-time from one save to the next save? morons.

that is an amazing discovery.