• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning

G7 S2F FSX carrier ops

kdfw

Charter Member
This is one nice airplane. The big radial engine makes some nice noise and works well with accufeel.

View attachment 75756View attachment 75758

View attachment 75757View attachment 75759
View attachment 75761View attachment 75760
View attachment 75762View attachment 75763

I had to add this to the aircraft.cfg to get the catapult to work:
[launch_assistance]
launch_bar_pivot = 11.00, 0.00, -7.25
launch_bar_lug = 11.00, 0.00, -7.25
and modified the tailhook so the plane will not topple over after an arrested landing (hook does sink into the surface though...):
[TailHook]
tailhook_length=8.428 ;(feet)
tailhook_position=-21.488, 0.0, 1
cable_force_adjust=0.65 //1.0
and some lighting tweaks using Dino's vc light and shockwave light:
[lights]
light.1= 4, 10, -1.6, 1.00, fx_t45_vclight
light.2= 4, 10, 1.6, 1.00, fx_t45_vclight
light.3= 5, 15.60, -1.25, -2.00, fx_shockwave_landing_light_small_old //fx_shockwave_landing_light_narrow
and replace fsx garmin with RXP GNS530 in the VC:
gauge09=rxpGNS!GNS530, 44,48,351,254
 
Nice, thank you. I was thinking about shockwave lights for the Stoof. The WillyFudd is a blast as well...

Some nice flying footage, if you've not seen it. CS2F's start hitting the deck around 4:00. Watch the tail wheel. Its interesting that a S2F operating aboard is pretty a quadricycle U/C. The SeaKings are flown on and off more like conventional aircraft in contrast with the current practice of pulling to a hover port side and translating on and off.



http://www.youtube.com/watch?v=qEqhm0MzEgM
 
Nice, thank you. I was thinking about shockwave lights for the Stoof. The WillyFudd is a blast as well...

Some nice flying footage, if you've not seen it. CS2F's start hitting the deck around 4:00. Watch the tail wheel. Its interesting that a S2F operating aboard is pretty a quadricycle U/C. The SeaKings are flown on and off more like conventional aircraft in contrast with the current practice of pulling to a hover port side and translating on and off.



http://www.youtube.com/watch?v=qEqhm0MzEgM


The flick ^ has some nice background music; sounds reminiscent of Richard Rogers and the NBC Orchestra musical scores of "Victory at Sea". I have the entire collection on DVD's.
 
This is one nice airplane. The big radial engine makes some nice noise and works well with accufeel.

View attachment 75756View attachment 75758

...snipped...
and modified the tailhook so the plane will not topple over after an arrested landing (hook does sink into the surface though...):
...snipped...

My experience is that if landing speeds and weights are correct, you should not have this problem. Keep landing fuel load below 50% and capture speed at 85-95. Of course if your angle of attack is too far from perpendicular to the wire .... :)
 
This is one nice airplane. The big radial engine makes some nice noise and works well with accufeel.

View attachment 75756View attachment 75758

View attachment 75757View attachment 75759
View attachment 75761View attachment 75760
View attachment 75762View attachment 75763

I had to add this to the aircraft.cfg to get the catapult to work:
[launch_assistance]
launch_bar_pivot = 11.00, 0.00, -7.25
launch_bar_lug = 11.00, 0.00, -7.25
and modified the tailhook so the plane will not topple over after an arrested landing (hook does sink into the surface though...):
[TailHook]
tailhook_length=8.428 ;(feet)
tailhook_position=-21.488, 0.0, 1
cable_force_adjust=0.65 //1.0
and some lighting tweaks using Dino's vc light and shockwave light:
[lights]
light.1= 4, 10, -1.6, 1.00, fx_t45_vclight
light.2= 4, 10, 1.6, 1.00, fx_t45_vclight
light.3= 5, 15.60, -1.25, -2.00, fx_shockwave_landing_light_small_old //fx_shockwave_landing_light_narrow
and replace fsx garmin with RXP GNS530 in the VC:
gauge09=rxpGNS!GNS530, 44,48,351,254

From the info I got from Euroastar, he coded the lights into the MDL so Shockwave lights won't work, I tried it (added shockwave lights date to the AIrcraft.cfg) and there was no difference.
I also could not get my searchlight to function without adding the searchlight effect from the old FS9 version to the FSX/Effects folder.
 
I land at around 85-90kts perpendicular to the wires with 30% fuel but it still tips over on the carrier so I modified the tailhook parms. I'll practice more and see if it improves, and try it while the carrier is moving.

As for shockwave light, it does work--at least you can add the landing light for the light cone effect. Other lights like nav and beacon are already baked into the mdl so you shouldn't use shockwave. I got the searchlight to work by copying and renaming one of the shockwave landing light "fx_searchlight.fx."

Landing light off/on with shockwave lights:
View attachment 75779View attachment 75780
 
This was quite extensively tested in FSX carrier ops. As Milton pointed out weight and speed must be correct, and there must also be wind over the deck. If AI Carriers is used the default speed of the ship is 25 knots. Typically real carrier ops will have about 40 knots over the deck with the wind shightly from the port side. In had a lot of discussion about this with my Naval Aviator cohorts. With the the ship steaming directly into the wind or no wind at all one needs to keep adjusting course to the right as the ship moves out of your flight path.

If you are doing everything correctly, the current aircraft works well indeed, if is not working, you are not in deck landing parameters. I probably made 200 deck landings developing this....

T
 
This was quite extensively tested in FSX carrier ops. As Milton pointed out weight and speed must be correct, and there must also be wind over the deck. If AI Carriers is used the default speed of the ship is 25 knots. Typically real carrier ops will have about 40 knots over the deck with the wind shightly from the port side. In had a lot of discussion about this with my Naval Aviator cohorts. With the the ship steaming directly into the wind or no wind at all one needs to keep adjusting course to the right as the ship moves out of your flight path.

If you are doing everything correctly, the current aircraft works well indeed, if is not working, you are not in deck landing parameters. I probably made 200 deck landings developing this....

T

Thanks for the reply, I'll check the winds again and practice some more. And yes, using ai carriers.
 
One of the cfg parameters involved here is the cable force adjust. Reducing this scalar makes for a longer and slower arrestment, longer cable runout. You just don't want to run out of deck! All of my testing was done on the new Enterprise, CVN 65.

Cheers: T
 
I land at around 85-90kts perpendicular to the wires with 30% fuel but it still tips over on the carrier so I modified the tailhook parms. I'll practice more and see if it improves, and try it while the carrier is moving.

As for shockwave light, it does work--at least you can add the landing light for the light cone effect. Other lights like nav and beacon are already baked into the mdl so you shouldn't use shockwave. I got the searchlight to work by copying and renaming one of the shockwave landing light "fx_searchlight.fx."

Landing light off/on with shockwave lights:
View attachment 75779View attachment 75780

KDFW: I sent you a PM on what you PM'd me on correction IRT the last line of the lights entry.

Thanks for your help.......
 
Check the cable force adjust parameter, mine had two entries here for some reason. Try 0.55 instead of 1.0 The 1.0 works, but the 0.5 is a better value and doesn't stop the plane so fast.

T
 
I land at around 85-90kts perpendicular to the wires with 30% fuel but it still tips over on the carrier so I modified the tailhook parms. I'll practice more and see if it improves, and try it while the carrier is moving.

As for shockwave light, it does work--at least you can add the landing light for the light cone effect. Other lights like nav and beacon are already baked into the mdl so you shouldn't use shockwave. I got the searchlight to work by copying and renaming one of the shockwave landing light "fx_searchlight.fx."

Landing light off/on with shockwave lights:
View attachment 75779View attachment 75780

I tried this and got essentially same results as I did when I just copied the fx_searchlight.fx file from the old FS9/Ported S2f3 files to my FSX file. Now
the diff between the code in the files is basically the same however, one clue to using this shockwave file was this tidbit of info in that file:


Shockwave version:

[ParticleAttributes.1]
Blend Mode=2
Texture=fx_shockwave_light.bmp <<<<<<<<< Guess this calls on different texture then the SOH version.
Bounce=0.00
Color Start=30, 30, 30, 255
Color End=30, 30, 30, 0
Jitter Distance=0.00
Jitter Time=0.00
uv1=0.00, 0.00
uv2=1.00, 1.00
X Scale Goal=0.00
Y Scale Goal=0.00
Z Scale Goal=0.00
Extrude Length=0.00
Extrude Pitch Max=0.00
Extrude Heading Max=0.00

SOH VERSION has this:

[ParticleAttributes.2]
Blend Mode=2
Texture=fx_2.bmp <<<< call on different texture file.
Bounce=0.00
Color Start=55, 52, 50, 255
Color End=55, 52, 50, 0
Jitter Distance=0.00
Jitter Time=0.00
uv1=0.00, 0.50
uv2=0.50, 1.00
X Scale Goal=0.00
Y Scale Goal=0.00
Z Scale Goal=0.00
Extrude Length=0.00
Extrude Pitch Max=0.00
Extrude Heading Max=0.00
 
Check the cable force adjust parameter, mine had two entries here for some reason. Try 0.55 instead of 1.0 The 1.0 works, but the 0.5 is a better value and doesn't stop the plane so fast.

T

yes, the cable force parm made a big difference. at 0.3, i'm able to land on a stationary nimitz without flipping over or going over the deck. with the nimitz steaming at 25kts, parm of 1.0 worked fine.

since i like to watch landing replay to grade the landing--ship has to be stationary-- i'll set my cable force parm to 0.3.

thanks for your help.
 
A little OT, but I wanted to say thank you to all the people involved in this project.
This is one of my favourite aircrafts for carrier ops - vey well done, and great fun to fly.
 
Dallas Ft Worth:

If you want to do a stationary carrier, set up a 25-30 knot wind aligned with the landing area in user defined weather, advanced, wind. Yes I know the instant replay is fun and and FSX moving carriers have issues with this!

Cheers. T
 
Adding light effect to the E1B FUDD

I land at around 85-90kts perpendicular to the wires with 30% fuel but it still tips over on the carrier so I modified the tailhook parms. I'll practice more and see if it improves, and try it while the carrier is moving.

As for shockwave light, it does work--at least you can add the landing light for the light cone effect. Other lights like nav and beacon are already baked into the mdl so you shouldn't use shockwave. I got the searchlight to work by copying and renaming one of the shockwave landing light "fx_searchlight.fx."

Landing light off/on with shockwave lights:
View attachment 75779View attachment 75780

I tried to copy and paste the same identical info to the E1B aircraft.cfg file and it dosen't appear to work. (assume planes were similiar only Fudd has a muffin top.)
Wasn't there a shockwave gauge file to add to the panel.cfg ?


[lights]
//#1=beacon #2=strobe #3=nav #4=cockpit #5=landing
//#6=taxi #7=recog #8=wing #9=logo #10=cabin
//index,type, long, lat, vert, fx_filename
//-------------------------------------------------
light.1= 5, 15.60, -1.25, -2.00, fx_shockwave_landing_light_small.fx
 
it works.

just add the landing light entry to the **existing** [lights] section like this, there are already beacons in the section:


[lights]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.1= 2, 10, -1.6, 1.00, fx_t45_vclight //fx_WoP3_P51_vclight_fluor
light.2= 2, 10, 1.6, 1.00, fx_t45_vclight //fx_WoP3_P51_vclight_fluor
light.3= 5, 15.60, -1.25, -2.00, fx_shockwave_landing_light_small_old // fx_shockwave_landing_light_small
light.4=1, -24.307, -11.204, 10.849, fx_shockwave_beacon_rotating_red // fx_beacon ,
light.5=1, -24.307, 11.204, 10.849, fx_shockwave_beacon_rotating_red //fx_beacon ,

use .fx files you have.



I tried to copy and paste the same identical info to the E1B aircraft.cfg file and it dosen't appear to work. (assume planes were similiar only Fudd has a muffin top.)
Wasn't there a shockwave gauge file to add to the panel.cfg ?


[lights]
//#1=beacon #2=strobe #3=nav #4=cockpit #5=landing
//#6=taxi #7=recog #8=wing #9=logo #10=cabin
//index,type, long, lat, vert, fx_filename
//-------------------------------------------------
light.1= 5, 15.60, -1.25, -2.00, fx_shockwave_landing_light_small.fx
 
Back
Top