problem with manual TDC in FOTRSU

[boonie]

hi,
i got the itch for some ship violencing recently and so i installed sh4+fotrsu from fresh. i was doing the tutorial for the 'manual tdc 90degree EZ' and discovered that no matter how carefully i do the manual data input, the stadimeter will always give me a wrong result, typically the main problem is it always give me a range that is like at least 1-2km further that where the actual ship is. and this always leads to the system getting the estimated speed at least 1-2 knot higher making it fail unless u are in extreme close range like less than 1.5km.


is this working as intended? or did i miss sumthing during installation? its a fresh sh4 install. i installed just the fotrsu without the additional stuff provided in the download page, did the LAA and even got the museum running.


oh and also ship id manual does not give the length of the ship.. so i cant use the 'time it took for ship crossing the hairline in periscope' method to estimate the speed so it kinda make the whole thing a bit too frustrating to aim properly..

[boonie]

hmm i am seeing this mistake in stadimeter across the whole fleet, all ship that i tried to manual tdc all give the same 1-2km extra range.


i am thinking it might be the periscope zoom problem. by increasing the zoom slightly i think it will make the ship bigger so when i do the stadimeter i will land the image at a higher place so it will give an accurate range when done accurately.


does anyone know where to adjust this?

[propbeanie]

For the "zoom", use the <Tab> key to go between the two possible zooms. The "zoom" in FotRSU was meticulously set by CapnScurvy after quite a bit of testing and adjusting and testing some more. You field of view and the zoom are as close to "real" as the game allows. That particular mission starts the player too close to the ship and does not give you sufficient time to do more than maybe two attempts at ranging and speed calculation. You do want to find the ship's course, and then get as close as you can to minimize any inherent errors. The stadimeter is only as accurate as your screen display, and as steady as your hand is... I usually just get within 1000 yards on the 90 and shoot at the 12-20 degree angle, depending upon the target's speed (Fast 90). Also, the SH4 owner's manual actually doesn't do too bad with the functionality of manual targeting (SilentHunter4 Manual.pdf)

[boonie]

hmm please dont ban me for stating this:


using stock sh4+ubm (steam) : got the range bang on the dot accurate on first try.


using fotrs v1.3 with steam sh4 : bang on the dot range accurate on first try.




not trying to belittle the hardwork of anyone but there's something seriously wrong with the stadimeter on fotrsu.

[KaleunMarco]

Originally Posted by boonie

hmm please dont ban me for stating this:


using stock sh4+ubm (steam) : got the range bang on the dot accurate on first try.


using fotrs v1.3 with steam sh4 : bang on the dot range accurate on first try.




not trying to belittle the hardwork of anyone but there's something seriously wrong with the stadimeter on fotrsu.

ban you...no.
take the mickey out on you....possibly.

de-install fotrs 1.3 and download and install FOTRSU 1.8.

[boonie]

nah.. i thought of going for v1.3. but that's too 2012..



finally figured how to get a sh4 patch 1.4 going after 1 night of trying. now i am running fotrs v2.0. although i only know 2 words in german 'panzerkampfwagen' and 'flammenwerf'... but they have working stadimeter. lol.

[propbeanie]

Had you emptied the Save folder, which defaults to C:\Users \UserName \Documents \SH4 after you activated FotRSU v1.8? It uses quite a few "assets" differently than the Stock or any other modded game, and if you do not empty the Save folder, the game does not run correctly. That also applies to most major mod configuration changes with JSGME, but is dependent upon what is changed when doing so. If you still have FotRSU activated, run its JSGME and choose "Tasks..." in the middle, then "Export activated mods list to --->" and choose either "Clipboard" or "Text file", and paste the info into your next post. As an aside, there is a partial English translation in the SubSim downloads somewhere for v2.x of FOTRS. It is a beautiful looking mod, and is what FotRSU was built on, along with combining v1.2 and v1.3 of the SH4v1.5 mods. You will most likely find that the AI is quite persistent in FOTRS v2.x

[boonie]

cant get the log now.. i already wiped out the sh4 v1.5. now i am on sh4v1.4 doing fotrs v2.0.


will look for the file tyvm its tough playing with full german language.. i am using a 2nd monitor to type out everything sent from radio in to google translate while pausing the game.. it however gave a strange vibe of working the enigma machine.. LMFAO...


ps:
is this the link u mentioned?

https://www.subsim.com/radioroom/sho...d.php?t=226278

the link on the top of the page that was supposedly leading to a translated version only leads to the same german version download page unfortunately.

[boonie]

initial testing of FOTRS v2.0 (ge):
-radar is not working. big disappointment.

-friendly unit dont seems to generate sound in hydrophone.i think this comes from stock.
-sometimes the sound just bug out and gives out a long super loud garble of noises. super annoying. encountered twice in few hours of play, happened during dive/surfacing when time compression is used.



not sure to continue with this or go back to fotrsu at this point.

[propbeanie]

Which boat are you in, and what year is it? FOTRS tried to have relatively accurate dates for both the SD and SJ radars, so it is like June 1942 before SD Air Search, and later for SJ Surface search.

There is an issue with at least one, possibly three ships in Stock that do not have the "sound" correct for sonar/hydrophones, and that is carried into FOTRS.

The Stock game mostly uses 44.1kHz, 16-bit audio, which would be "CD Quality", for the wave file sounds. Speech is mostly ogg vorbis. Music might be mp3 or wav. The 'modern' computer is usually running at 48kHz at 24-bit depth, since most of the online movies are at that or at 16-bits. That can sometimes lead to issues with older DirectX v9 games, such as SH4. Also, if I'm not mistaken, there are a few sounds in FOTRS that are not "Stock game compliant", and are either lower in frequency or bit-depth, which can throw the game's audio engine off. However, another factor could be if you hadn't deleted the Save folder after activating the mod, which could also contribute to radar, sonar and hydrophone issues. The only "problem" with FOTRS (besides the language barrier) is the number of what I call "run-away spawns" that occur, mostly from Japanese ports with IJN DD that were not docked properly, or were not terminated properly. I thought I had a "fix" posted for that on SubSim here, but cannot find that. I'll try to dig that out of the old computer and re-upload it.

[boonie]

i am not sure if i have removed the save files in btwn the operation. will reinstall another round to get to the bottom of it..


in my fotrs v2.0 i started at 8th dec right after pearl harbor. when i go to sub component screen at base there are SD radar already installed on my sargo boat. but no air radar installed nor in store yet. and when i go for the 1st patrol both the air and sea radar is not working . as in, i cant flip the switch to turn on the thing.


i am even beginning to enjoy working the enigma machine. its weird coz i am supposed to be on the american side.

[GWB]

Fresh / clean install - same issue. See image I attach below for further details

I'm new here, so do check over my image for obvious mistake. Joining only the other day, so I could just be screwing things up. I follow the instructions, including deleting the documents / savegames folder, and on the face of it, have a somehwat fully working SH4 v1.5 + FotRSU v1.8 install. I done the 2GB memory hack thing, and installed the game outside programfiles.


My modded game works fine EXCEPT when I turn the difficulty settings up (ie manual targeting). When it comes to tracking the enemy ship, the speed does not translate onto the TDC and update, my torpedoes constantly fire at where the target was when I fire them (ie speed = 0). The only way round this is to guestimate where the target will be, and point the periscope in that direction.

I tried the same career on easy, and the thing just automatically lines up and hits the target with zero effort, which I find removes all challenge.

Note that when I user the sonar/hydro operator, he will give me accurate target range also, but it does also not track/update with the speed, so either way of doing this doesn't work for me.

Otherwise everything (in so far as I can tell) appears to work. The radar seems a little bit dodgy, but I've found just turn it off and on again, then force a sweep fixes the issue.

Any help regarding the TDC really appreciated (I am new to this game, only bought it last week and installed FotRSU based on friendly community advice)

[GWB]

this is frustrating because my lengthy post with attached image just got deleted where i tried to highlight the same issue.

I'm new here, so clean SH4 / FotRSU installation, following the instructions. The whole setup seems to work fine & as intended, UNLESS I turned the TDC difficulty up (which is what I want).

When this happens, the whole process of using periscope to ID the enemy ship, get range, AoB and so forth seems to work perfectly, but once the speed is sent over (which the TDC accepts by its own account) the target information is NOT kept updated, despite the scope being "locked" on target. The range to target does NOT tick down.

In addition to this, firing the torpedos fires them wherever the scope is looking, and not into the projected path of the ship, based on speed + angle and all that good stuff. I even unlocked the periscope to try and guestimate where target would be once the torp covered distance to target, and to my suprise, the torpedo still fired directly towards the ship (even though it was about 20 degrees off the bow!)

Somehow, my speed inputs are not being made use of by either the TDC for ship tracking purposes, nor the gyro settings on the torpedoes to make their initial turns towards target.

My screenshot shows the passage of time (stiched 2 together) with no change on the range. It shows the target is locked, the AoB was appx 40-45 degrees Starboard (ie approaching) and speed was set at 11kts (which the TDC shows as being accepted, alongside range).

The range was roughly 2500-3000 yards if memory serves, but it was NOT ticking down as the seconds went on by. Come to think of it, none of the values were updating, including AoB etc, all of which I updated several times, hoping at some point the TDC would "take hold".

Can anyone think of any ideas, short of playing this game on easy, which is exactly not what I wanted.


PS I did the install & activation instructions, including to install outside programfiles, the 4GB Memory address hack thing, and the running then deletion of docs / sh4 savegames folder contents... And otherwise the thing seems to work perfectly. Thanks in advance

[razark]

Originally Posted by GWB

The range was roughly 2500-3000 yards if memory serves, but it was NOT ticking down as the seconds went on by. Come to think of it, none of the values were updating, including AoB etc, all of which I updated several times, hoping at some point the TDC would "take hold".

I have not used FotRSU, but from the screenshots, it looks like you haven't turned on the Position Keeper.


Click that button next to the Position Keeper and Torpedo Settings labels, and it will light up. Then you should see the TDC values updating.

[1Patriotofmany]

Originally Posted by razark

I have not used FotRSU, but from the screenshots, it looks like you haven't turned on the Position Keeper.


Click that button next to the Position Keeper and Torpedo Settings labels, and it will light up. Then you should see the TDC values updating.

I don't use manual but I'm going to bet you nailed it on the head.