RV HIEN (PAKAKAN) BV 138

[SgtT]

I thought I would create a new thread instead of hijacking the other BV-13 thread to ask my question concerning RV HIEN (PAKAKAN) BV 138.

Based upon the info that Napamule provided I was able to get the panel and the sound to work somewhat.

On the sound, I have sound when I'm in the panel view but no sound when I switch to an outside view.

Any suggestions on how to fix this would be appreciated.

Thanks,

T.

[napamule]

He he. You are trying to make a OLD sound (1999) work, and it is useless. Unless you can re-write the sound.cfg. Go get some decent sounds. They CAN be CFS, FS2k, or FS2k2. As long as there is some 'recent' format used for the sound.cfg. There are some really 'fancy' sound cfgs out there. Even have wind, door shut, etc sounds. This baby has 3 engines, so at least a sound.cfg that list/call 2 engines should be used.

I uploaded a cfg and (my version of air file) for Mr Hein's GE BV-138MS over at the highjacked (hehe) thread. Took me about 2 1/2 hours but I already had a 'template' for use with Ito's BV-138G, so it was easy money. Let me see if I can post it here and then the Admins can remove it from the other place. We need a thread for each of Ito's models. That way we can come and go from one to the other without getting lost in the forums (I keep losing my threads!). I have FDE's for about 6 of his models. I should start thread, post updated FDEs (zip file), and go from there. Here is zip.
Chuck B
Napamule

[SgtT]

Thanks, I'll giove that a try. Can I use it also for the C model or is there something else that needs to be changed?

Thanks,

T.

[napamule]

Well, the files (cfg and air) 'fit' both Hien's MS and G models, according to Hurricane2. All you need to do is change 'Title=xx' line to fit what you had. The line 'model= ' is blank so it goes to what ever model folder (ie: 'model= ') you have. The model ties in mostly with texture variation (ie: 'paint'). So my FDEs will work with both. But they MUST be used together due to parameters, names, etc. I only have 1 paint ('texture= ') so you might have to add your (flightsim.x) sections for other paints.

What I would like to know is: 'did they work' (better)? If they didn't don't tell me. Just kidding. I know-time-not enough time to fly sometimes. Tamale is good. Cheers.
Chuck B
Napamule

[SgtT]

Thanks, I'm going to try it out tomorrow and see how it does. Appreciate the help and look forward to trying it out.

T.

[napamule]

SgtT,
Flying the MS variation just now I noticed the water rudder was causing it to shake like crazy. So, that's problem #1 I need to try to fix. Will update tomorrow, I hope. Usually giving the rear floats steering capability eliminates the need for water rudder. But I can not seem to figure why that 'trick' won't work with this model. Oh, well. I'll just use a bigger hammer on it tomorrow. What kind of mess did I get myself into?

Then when the engines were starting, the puff of smoke was not coming from the spinning engine but from the other engine. Drats! So I worked on that and will incude in update. And (of course) the (smoke) section had to also be wrong. It was. Worked on that. With 3 engines things get a little 'sticky' as it's 'unorthodox'. The prudent thing would of been to only have given it 2 engines. But NO, I have to go mess around with 3 engines (hehe). I learn something new every day (for the past 5 years) and am not done learning yet-evidently. Cheers.
Chuck B

[napamule]

Hold it. I made a mistake. Here is the updated cnt pts for Hien's BV-218MS (and G) models. I left out steering for floats. I wondered what it wasn't turning. Shock. Pure shock. Goofed big time. So copy paste to cfg and now it turns (and doesn't crash). Sorry about the mix up. I was trying to test water rudder shaking and removed the steering so it wouldn't interfere. Yeah, right. Forgot to put them back. Cheers.

--------------------------------------------------------------------------------
Hien BV-218MS (and G) models, UpDated cnt pts: (11Jul22).
[contact_points]
//Wheels
point.0= 1, 23.99, -5.00, -8.80, 1574.80, 0, 0.690, 30.00, 0.400, 2.5, 0.86, 5.0, 5.0, 0, 0.0, 0.0
point.1= 1, 23.99, 5.00, -8.80, 1574.80, 0, 0.690, 30.00, 0.400, 2.5, 0.86, 5.0, 5.0, 2, 0.0, 0.0
point.2= 1, -12.99, -4.90, -8.60, 1574.80, 1, 0.690, 0.00, 0.400, 2.5, 0.86, 5.0, 5.0, 3, 0.0, 0.0
point.3= 1, -12.99, 4.90, -8.60, 1574.80, 2, 0.690, 0.00, 0.400, 2.5, 0.86, 5.0, 5.0, 5, 0.0, 0.0
//Floats
point.4= 4, 16.00, -3.33, -8.44, 15574.80, 0, 0.512, 0.00, 0.300, 4.5, 1.00, 0.0, 0.0, 1, 0.0, 0.0
point.5= 4, 16.00, 3.33, -8.44, 15574.80, 0, 0.512, 0.00, 0.300, 4.5, 1.00, 0.0, 0.0, 1, 0.0, 0.0
point.6= 4, -16.00, -2.50, -8.44, 15574.80, 0, 0.512, 30.00, 0.300, 4.5, 1.00, 0.0, 0.0, 1, 0.0, 0.0
point.7= 4, -16.00, 2.50, -8.44, 15574.80, 0, 0.512, 30.00, 0.300, 4.5, 1.00, 0.0, 0.0, 1, 0.0, 0.0
//Pontoons
point.8= 4, 2.50, -30.80, -8.25, 15574.80, 0, 0.512, 0.00, 0.350, 4.5, 1.00, 0.0, 0.0, 1, 0.0, 0.0
point.9= 4, 2.50, 30.80, -8.25, 15574.80, 0, 0.512, 0.00, 0.350, 4.5, 1.00, 0.0, 0.0, 1, 0.0, 0.0
//Water Rudder(s) -- Not Needed -- Included for 'testing' only ---
//point.10= 5, -17.00, -5.00, -8.50, 15574.80, 0, 0.000, 30.00, 0.000, 0.0, 1.00, 2.0, 2.0, 1, 0.0, 0.0
//point.11= 5, -17.00, 5.00, -8.50, 15574.80, 0, 0.000, 30.00, 0.000, 0.0, 1.00, 2.0, 2.0, 1, 0.0, 0.0
//
static_pitch=0.000000
static_cg_height= 9.600
gear_system_type=1


[GeneralEngineData]
// (Lon, Lat, Vert)
engine_type=0
Engine.0= 12.000, 12.000, 6.000
Engine.1= 12.000, -12.000, 6.000
Engine.2= 11.000, 0.000, 8.000
fuel_flow_scalar= 0.650 //1.000
min_throttle_limit= -0.499 //-0.399

[SMOKESYSTEM]
// (Vert, Lon, Lat ) (smoke is lower, shorter & wider position)
smoke.0= 6.00, 10.00, 14.00, fx_smoke_w,
smoke.1= 6.00, 10.00, -14.00, fx_smoke_w,
smoke.2= 8.00, 9.00, 0.00, fx_smoke_w,

(I hope I never do this (silly mistake) again. It's very embarassing. Am I fired? (ha)).

[Navtech]

Thank you very much Napamule ... all run smooth :)

[SgtT]

Napamule ,

Just want to make sure I'm doing this right, just cut and paste what you posted into the aircraft.cfg file. Do I need to do anything else, does it matter where it goes in the aircraft.cfg file?

Thanks again for the help,

T.

[napamule]

SgtT,
Right on. Just start from (contact_points) line down to 'gear system type' (press & hold left mouse button and drag down. Right click highlighted text. Click 'Copy'. Then open cfg and click next (to left) of your (contact_points). Then hit 'Enter' to move it down and make a 'space'. Place cursor there with mouse click. Right click mouse to get menu and choose 'Paste'. Then comment out your (cnt pts) by placing '//' before each line, all the way down. Now do 'File/Save' then click 'Yes' to overwrite (which is not 'true' overwrite as you still have the old section there, but is 'commented out'). That is the way I do it.

But, butt, cigerete butt: You get the whole cfg in the zip with the 'updated' FDEs (for Hien's BV-138-found earlier in thread). Why stuggle. Just rename your present aircraft cfg to something like 'old.aircraft.cfg' and then you can put my cfg there in same folder without deleting your cfg. Tricks of the trade. Cheers.
Chuck B
Napamule