[REL] RFB/Real Fleet Boat for 1.5

[DaveP63]

First mission out of Pearl with the Drum. About 200 miles of the coast of Japan I encountered a large Maru. Fired 3 fish and got three hits. Two on the Maru and one on the Drum with a circular run! Awesome Job

[ustahl]

Originally Posted by Kruger

I stumbled upon this flickering issue myself.

What's the command to close a torpedo tube?

In (my) data\cfg\commands.cfg there are following entries for opening & closing torpedo tubes:

-------
[Cmd308]
Name=Open_torpedo_tube
Ctxt=1

[Cmd309]
Name=Close_torpedo_tube
Ctxt=1

[Cmd310]
Name=Open_sel_torpedo_tube
Ctxt=1
Key0=0x51,,"Q"

[Cmd311]
Name=Close_sel_torpedo_tube
Ctxt=1

[Cmd312]
Name=Toggle_open_close_torpedo_tube
Ctxt=1
--------

It shows that a specific command for closing a tube is not set.
I've been using Cmd310 only to open the selected tube by pressing "Q", as it closes automatically after firing the torpedo.
I guess that if you edit this file with notepad by moving "Key0=0x51,,"Q"" at the end of Cmd312, you could use "Q" for togglin the tube open/close.
Make a backup of your commands.cfg before fiddling .

[Orion2012]

Originally Posted by ustahl

Good question! In order to answer your question, I risked my life surfacing in the midst of the Battle off Samar, close to Yamato, Kongo etc...:rotfl:
The superstructure flickering occurs only when looking through the periscope - looking through the TBT or binocular all textures are faultlessly stable, i.e. no flickering. As mentioned earlier, I've also tested different periscope mods, but the flickering remains. Hense the culprit can't be the RFB 1.52 periscope file(s).

As I'm now running PE4 on top of RFB 1.52 in order to avoid the ugly flickering, I wonder if this (doubling PE4) might cause some undesired side-effects.
I don't think it is my graphic card (Evga 8800GTS 640MB) with newest nVidia driver, or could it be?

Another benefit of adding PE4 after RFB 1.52 is the improvement of Yamato's skin/textures. In single RFB 1.52 Yamato has both the huge & ugly stock portholes & textures plus the improved smaller portholes & textures from RFB 1.52's PE4, i.e. a mixture of stock AND improved (Kriller?) textures. It's a mixture of two texture sets showing (conflicting) details of both.
The added PE4 corrects this and shows Yamato with improved textures only.
Maybe this texture mixture is a clue to the flickering issue??

Thanks for the info. I can confirm its not the graphics card. Tried the mod on both an Alpha OC 8800 and an ATI 1900XTX and the flickering occurs on both.

"Q" both opens and closes the torpedo doors.

[ustahl]

Originally Posted by Orion2012

Thanks for the info. I can confirm its not the graphics card. Tried the mod on both an Alpha OC 8800 and an ATI 1900XTX and the flickering occurs on both.

Good to know, thanks. Have you tried enabling an extra PE4 on top of RFB 1.52, and whether that fixes the flickering for you as well, like it did for me? Alternatively, adding Environmental 5.0 on top of RFB 1.52 fixes the flickering for me, too. Any findings?

[Bosje]

The walking around your sub-part and anything else on the visual front is absolutely brilliant but I'm not having any fun when the enemy is about. And this is coming from a hardcore GWX veteran

no sinkings yet. cant lock, cant even plot except by radar when there's a slight fog, when you finally hit a ship it doesnt go down and when they hit you you're dead. one shell to my engine compartment is all it took. This is a whole new brand of realism I guess, sure takes some getting used to.

My questions:
I posted earlier about the binocular camera. I am unable to fix the clipping distance myself, could anyone please help me out to put the obstructions back on the bridge? I loved that part of the old RFB. And any word on the dive command yet?

cheers

[Rockin Robbins]

RFB Team (so far)

Anyone who's allowed us to use their mod- see the list here

Direct contributors and/or testers- Beery, LukeFF, Raymond6751, Wilcke, DeepIron, Capn Scurvy, PantherHercules, AVGWarhawk, CCIP, Donner, Nuc, lurker_hlb3, Ducimus, AkbarGulag, RockinRobbins, swdw, Carotio, Observer, Der Teddy Bar, Monolith, Peto, fireship4, Rockin Robbins, Gunfighter, Fearless, CDR Resser, Donner, skwasjer

Honorary- LeoVampire, kv29, kriller2, sober, and SteveTRM, John Hamm, who've allowed us to merge some of their changes with RFB files, answered my questions and given great advice.

Thanks to lurker_hlb3 for making RSRD and OM compatible with RFB.

A SPECIAL thanks to skwasjer; w/o his S3D much of this would not happen.

What in Sam Hill is goin' on here???? Why do I get TWICE AS MUCH BLAME?There's plenty of blame to go around without socking me TWICE!

[lurker_hlb3]

Originally Posted by Orion2012

Thanks for the info. I can confirm its not the graphics card. Tried the mod on both an Alpha OC 8800 and an ATI 1900XTX and the flickering occurs on both.

"Q" both opens and closes the torpedo doors.

IRT the " flickering"



I did a controlled binary file comparison between PE4 Main & RFB152. The only different files found are as follows:


Misc

Wake_Back.tga ( PE4 newer )
Wake_Front.tga (PE4 newer )

Sea

NBB_Yamato_N01.dds ( only in PE4 )


SubmarineSchool

NSS05 Scope Measuring ( only in PE4 )

[LukeFF]

Originally Posted by kwbgjh2

No that i have completed my first mission whith this this beautiful mod here is my summary:

You have done a real great work to amplify the game's challenges.

I have only ONE point of criticism on the new damage model, and that is the the drive propulsion of the merchants.

Look at this pictures:

BUT.... i measured the merchant before firing about 12 knots. I gave him six strikes and absolutly unimpressed it steamed away with 10 knots.

I am really ok with the long sinking time... but round about 1800 kg Torpex and no abrasion, breach or any else damage to the propulsion system?

2 game weeks later a nearly like adventure. At best weather another sight of merchant. Trying to come infront of him he discovered me. Speed slowed down from 12 knots to 6 knots and it started to zigzagging. But i got him. Again six fish. 4 Impact, 2 dudes. And... the merchant accelareted to 12 knots and forced me to surface just to follow him.

Unfortunately, what you've encountered is a flaw in the game's AI coding. Unless you hit the ship's propulsion system (e.g., a propeller shaft or propeller), the ship will continue to sail on so long as the flooding has not caused the ship to sink. Many a thread and screenshot have shown this behavior.

[LukeFF]

Originally Posted by Arclight

1 below the fore mast, 1 below the bridge, 1 in the engine rooms and 1 below the aft mast. I thought that was d**n near perfect. You yourself always say you aim for the masts and midships, or am I missing something?

Don't get me wrong, I wasn't complaining about the modeling. I chalk it up to the Mark 10s, I've switched to a fleetboat now and the Mark 14s don't leave much afloat when spaced like that.

Which ship was this?

[LukeFF]

Originally Posted by ustahl

The superstructure flickering occurs only when looking through the periscope - looking through the TBT or binocular all textures are faultlessly stable, i.e. no flickering. As mentioned earlier, I've also tested different periscope mods, but the flickering remains. Hense the culprit can't be the RFB 1.52 periscope file(s).

As I'm now running PE4 on top of RFB 1.52 in order to avoid the ugly flickering, I wonder if this (doubling PE4) might cause some undesired side-effects.
I don't think it is my graphic card (Evga 8800GTS 640MB) with newest nVidia driver, or could it be?

Another benefit of adding PE4 after RFB 1.52 is the improvement of Yamato's skin/textures. In single RFB 1.52 Yamato has both the huge & ugly stock portholes & textures plus the improved smaller portholes & textures from RFB 1.52's PE4, i.e. a mixture of stock AND improved (Kriller?) textures. It's a mixture of two texture sets showing (conflicting) details of both.
The added PE4 corrects this and shows Yamato with improved textures only.
Maybe this texture mixture is a clue to the flickering issue??

The flickering is a mystery to me. I would suggest one start by looking at the DummyCam_Periscope and ObPeriscope sections in Cameras.dat to see if something is amiss. At this point that's the only place I can surmise a problem exists at the moment.

Found out the problem with the Yamato textures, as listed by Lurker below. Will likely be part of an upcoming patch to fix a few problems with RFB.

[LukeFF]

Originally Posted by ustahl

Good to know, thanks. Have you tried enabling an extra PE4 on top of RFB 1.52, and whether that fixes the flickering for you as well, like it did for me? Alternatively, adding Environmental 5.0 on top of RFB 1.52 fixes the flickering for me, too. Any findings?

Enabling PE4 "extra" on top of RFB will not solve any problems but rather cause conflicts with RFB, since the two mods on their own are not compatible. Obviously there is a setting in PE4 not carried over to RFB that is causing the flickering problem. I would suggest starting by copying over PE4's Cameras.dat file to see if that solves the problem and then take it from there.

[Quagmire]

Originally Posted by LukeFF

Unfortunately, what you've encountered is a flaw in the game's AI coding. Unless you hit the ship's propulsion system (e.g., a propeller shaft or propeller), the ship will continue to sail on so long as the flooding has not caused the ship to sink. Many a thread and screenshot have shown this behavior.

WHAT!?@!?! Man SHIV is a real let down from SHIII in this regard. I remember plugging merchants below the funnel and consequently destroying the engine, bringing the ship to a halt. This happened in SHIII all the time. You mean to tell me that a ship can be full of holes, the engine room can be completely flooded and as long as the propeller or shaft isn't damaged it will plow along at flank speed until it sinks?!

We need to find a work around for this foolishness...
.

[LukeFF]

Originally Posted by Quagmire

WHAT!?@!?! Man SHIV is a real let down from SHIII in this regard. I remember plugging merchants below the funnel and consequently destroying the engine, bringing the ship to a halt. This happened in SHIII all the time. You mean to tell me that a ship can be full of holes, the engine room can be completely flooded and as long as the propeller or shaft isn't damaged it will plow along at flank speed until it sinks?!

Ach, I should have corrected what I wrote above to include "hitting the engine compartments." As designed, a ship will stop or slow down when the following are destroyed:

• Engine Room
• Propeller Shaft
• Propeller

Note that a ship with multiple funnels will continue to move through the water at a reduced speed until all engine rooms are completely flooded or the ship sinks.

Sorry about that accidental bit of dis-information.

[kjuice]

Just comming back into sh4, and wanted to get the RFB for it. I installed sh4, and patch. then jsme. once done, put RFB 1.52 in mods folder. enabled it with jsme. upon running, I get a

"file not found: data/menu/data/black80"

popup on windows. after that i get

" there is a new(not implimented) page:<page chooseloadsave>!"

after that i get

"file not found: data/menu/gui/tdc/tdc_metric.tga"

thats as far as i can get, what did i do wrong guys?

[Fish40]

Kjuice, which patch are you referring too? Are you updated to the latest 1.5 U Boat addon? This is the latest (cost $10) for which most, if not all the mods are based. Do a quick search, and I'm sure you'll find a link for the addon, AKA v1.5. I'ts worth it!