Jump to content

HELP - Helo wont float!


Allen24

Recommended Posts

In the aircraft.cfg file, there is a section [Contact_points]. In that, there should be 4 lines that look like this: point.3 = 4, 16, -19.494, 12.909, 1500, 0, 1, 90, 0.3, 2.5, 0.7, 10, 12, 0, 200, 200

Note the 4 right after the equals sign. That designates the line to be a float type of contact point. IF you don't have those lines, we will need to create them and add them into the Contact Points section.

If they are there, they need adjusting to prevent the "crash" problem.

Can you post the [Contact_points] section of your aircraft.cfg so we can see where-in lieth the rub, so to speak.

Hope this helps a little :)

Pat☺

[sIGPIC][/sIGPIC]

Had a thought...then there was the smell of something burning, and sparks, and then a big fire, and then the lights went out! I guess I better not do that again!

Sgt, USMC, 10 years proud service, Inactive reserve now :D

Link to comment
Share on other sites

Thanks, I'm new at this. Here is the requested info:

 

[contact_points]

point.0= 3.000, 5.242, 3.369, -5.850, 1574.800, 0.000, 0.519, 0.000, 0.300, 2.500, 0.605, 0.000, 0.000, 2.000, 0.000, 0.000

point.1= 3.000, -4.166, -3.369, -5.850, 1574.800, 0.000, 0.519, 0.000, 0.300, 2.500, 0.728, 0.000, 0.000, 3.000, 0.000, 0.000

point.2= 3.000, -4.166, 3.369, -5.850, 1574.800, 0.000, 0.519, 0.000, 0.300, 2.500, 0.728, 0.000, 0.000, 3.000, 0.000, 0.000

point.3= 3.000, 5.242, -3.369, -5.850, 1574.800, 0.000, 0.519, 0.000, 0.300, 2.500, 0.605, 0.000, 0.000, 2.000, 0.000, 0.000

point.4= 2.000, 17.536, 0.000, 4.589, 100.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 7.000, 0.000, 0.000

point.5= 2.000, -17.536, 0.000, 4.589, 100.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 8.000, 0.000, 0.000

point.6= 2.000, 0.000, 17.536, 4.589, 787.400, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 6.000, 0.000, 0.000

point.7= 2.000, 0.000, -17.536, 4.589, 100.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 5.000, 0.000, 0.000

point.8= 2.000, -24.557, 0.000, 4.862, 500.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 4.000, 0.000, 0.000

point.9= 2.000, -22.654, 0.000, -2.880, 800.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 9.000, 0.000, 0.000

point.10= 2.000, -15.754, 1.256, 0.311, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 4.000, 0.000, 0.000

point.11= 2.000, -15.754, -1.256, 0.311, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 4.000, 0.000, 0.000

point.12= 5, -30.90, -5.250, -7.300, 1600, 0, 0.00, 50.0, 0.0, 0.0, 1.00, 1.0, 1.2, 0, 0.0, 0.0

point.13= 5, -30.90, 5.250, -7.300, 1600, 0, 0.00, 50.0, 0.0, 0.0, 1.00, 1.1, 1.5, 0, 0.0, 0.0

static_pitch = 0.100

static_cg_height = 5.800

Link to comment
Share on other sites

There are no '4' type contact points and that is why it won't float. Check you PM (Personal Messages).

Chuck B

Napamule

i7 2600K @ 3.4 Ghz (Turbo-Boost to 3.877 Ghz), Asus P8H67 Pro, Super Talent 8 Gb DDR3/1333 Dual Channel, XFX Radeon R7-360B 2Gb DDR5, Corsair 650 W PSU, Dell 23 in (2048x1152), Windows7 Pro 64 bit, MS Sidewinder Precision 2 Joy, Logitech K-360 wireless KB & Mouse, Targus PAUK10U USB Keypad for Throttle (F1 to F4)/Spoiler/Tailhook/Wing Fold/Pitch Trim/Parking Brake/Snap to 2D Panel/View Change. Installed on 250 Gb (D:). FS9 and FSX Acceleration (locked at 30 FPS).
Link to comment
Share on other sites

Ok, I'm sorry if I was misunderstood. Just changing a 3 to a 4 isn't really the solution. What we need to do is ADD some pointx=4... lines. At least 4 of them, to make it stable when floating.

The 3 type points are a necessary entry. IE: The helicopter needs them to land, detect craches, and so on. Thus, just changing 3's to 4's won't do what needs to be done.

I'll work on doing the additions for you. It may take me a day or so (other duties now that the weather is spring-like finally :D ). I suspect that may be what Chuck sent you, but I may well be wrong, so I'll work up my own set and see what happens.

 

I hope that's acceptable to you...

Pat☺

[sIGPIC][/sIGPIC]

Had a thought...then there was the smell of something burning, and sparks, and then a big fire, and then the lights went out! I guess I better not do that again!

Sgt, USMC, 10 years proud service, Inactive reserve now :D

Link to comment
Share on other sites

Pat,

He sent me a zip of the AS350 BE. It has floats in that cfg. Here they are. I flew and landed it on water - no crash. Did he remove the type 4 (floats) from cnt pts section? Maybe?

[contact_points]

point.0= 3.000, 5.242, 3.369, -5.850, 1574.800, 0.000, 0.519, 0.000, 0.300, 2.500, 0.605, 0.000, 0.000, 2.000, 0.000, 0.000

point.1= 3.000, -4.166, -3.369, -5.850, 1574.800, 0.000, 0.519, 0.000, 0.300, 2.500, 0.728, 0.000, 0.000, 3.000, 0.000, 0.000

point.2= 3.000, -4.166, 3.369, -5.850, 1574.800, 0.000, 0.519, 0.000, 0.300, 2.500, 0.728, 0.000, 0.000, 3.000, 0.000, 0.000

point.3= 3.000, 5.242, -3.369, -5.850, 1574.800, 0.000, 0.519, 0.000, 0.300, 2.500, 0.605, 0.000, 0.000, 2.000, 0.000, 0.000

point.4= 2.000, 17.536, 0.000, 4.589, 100.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 7.000, 0.000, 0.000

point.5= 2.000, -17.536, 0.000, 4.589, 100.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 8.000, 0.000, 0.000

point.6= 2.000, 0.000, 17.536, 4.589, 787.400, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 6.000, 0.000, 0.000

point.7= 2.000, 0.000, -17.536, 4.589, 100.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 5.000, 0.000, 0.000

point.8= 2.000, -24.557, 0.000, 4.862, 500.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 4.000, 0.000, 0.000

point.9= 2.000, -22.654, 0.000, -2.880, 800.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 9.000, 0.000, 0.000

point.10= 2.000, -15.754, 1.256, 0.311, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 4.000, 0.000, 0.000

point.11= 2.000, -15.754, -1.256, 0.311, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 4.000, 0.000, 0.000

point.12= 5, -30.90, -5.250, -7.300, 1600, 0, 0.00, 50.0, 0.0, 0.0, 1.00, 1.0, 1.2, 0, 0.0, 0.0

point.13= 5, -30.90, 5.250, -7.300, 1600, 0, 0.00, 50.0, 0.0, 0.0, 1.00, 1.1, 1.5, 0, 0.0, 0.0

point.14= 4.000, 5.242, 3.369, -4.543, 1574.800, 0.000, 0.519, 0.000, 0.300, 2.500, 0.605, 0.000, 0.000, 2.000, 0.000, 0.000

point.15= 4.000, -4.166, -3.369, -4.543, 1574.800, 0.000, 0.519, 0.000, 0.300, 2.500, 0.728, 0.000, 0.000, 3.000, 0.000, 0.000

point.16= 4.000, -4.166, 3.369, -4.543, 1574.800, 0.000, 0.519, 0.000, 0.300, 2.500, 0.728, 0.000, 0.000, 3.000, 0.000, 0.000

point.17= 4.000, 5.242, -3.369, -4.543, 1574.800, 0.000, 0.519, 0.000, 0.300, 2.500, 0.605, 0.000, 0.000, 2.000, 0.000, 0.000

static_pitch = 0.100

static_cg_height = 5.800

 

Here is video of me landing it on water:

 

PS: I just could be a combination of crash detection ON and the nose and tail scrapes causing problem. Also the water rudder (5) are way too low I think (-7.300).

 

Chuck B

Napamule

i7 2600K @ 3.4 Ghz (Turbo-Boost to 3.877 Ghz), Asus P8H67 Pro, Super Talent 8 Gb DDR3/1333 Dual Channel, XFX Radeon R7-360B 2Gb DDR5, Corsair 650 W PSU, Dell 23 in (2048x1152), Windows7 Pro 64 bit, MS Sidewinder Precision 2 Joy, Logitech K-360 wireless KB & Mouse, Targus PAUK10U USB Keypad for Throttle (F1 to F4)/Spoiler/Tailhook/Wing Fold/Pitch Trim/Parking Brake/Snap to 2D Panel/View Change. Installed on 250 Gb (D:). FS9 and FSX Acceleration (locked at 30 FPS).
Link to comment
Share on other sites

Did he remove the type 4 (floats) from cnt pts section? Maybe?

Well, Chuck, from what he posted above it looks like that's what happened.

His listing of points ends at point13, and the floats in the cnt_point you posted start at 14.

I don't know if he just didn't show the entire section, or if he cut point14 and on out for some reason.

Funny, I took what he posted and added float points that look exactly like what you posted. Honest, I don't have the zipfile for that chopper, but my float points look almost exactly like what you posted.

 

I don't know what's going on with his bird, although I suspect it has to do more with the scenery package he's using than his helicopter. I've found that quite often, helicopters trying to land on add-on sceneries get a crash detected. Some, you just need to fly into the area and you get a crash detected.

 

Other than all of the above, I am not sure what else may be going on.

Thanks for your help, though, Chuck! You're better at this stuff than I am :)

Pat☺

[sIGPIC][/sIGPIC]

Had a thought...then there was the smell of something burning, and sparks, and then a big fire, and then the lights went out! I guess I better not do that again!

Sgt, USMC, 10 years proud service, Inactive reserve now :D

Link to comment
Share on other sites

He stoped communicating with us so what you said about scenery crash might be true. Or he removed the floats, thinking they were the culprit. Too much mechanics and not enough 'diagnostics' (hehe). Hope he checks in. He needs to let us try to fix whatever is wrong. No fun crashing sim and not been able to fly due to some minor glitch (we caused). We all have 'Been there - done that'. Right?

Chuck B

i7 2600K @ 3.4 Ghz (Turbo-Boost to 3.877 Ghz), Asus P8H67 Pro, Super Talent 8 Gb DDR3/1333 Dual Channel, XFX Radeon R7-360B 2Gb DDR5, Corsair 650 W PSU, Dell 23 in (2048x1152), Windows7 Pro 64 bit, MS Sidewinder Precision 2 Joy, Logitech K-360 wireless KB & Mouse, Targus PAUK10U USB Keypad for Throttle (F1 to F4)/Spoiler/Tailhook/Wing Fold/Pitch Trim/Parking Brake/Snap to 2D Panel/View Change. Installed on 250 Gb (D:). FS9 and FSX Acceleration (locked at 30 FPS).
Link to comment
Share on other sites

  • 2 weeks later...

Sorry, I was out of town.

I don't understand this contact point stuff at all.

Do I just copy/paste the cfg posted above?

My points stop at 13. I did not adjust anything.

EDIT:

I want to thank you all. I copied the configuration posted above by Chuck.

Everything is working great now! Must land almost perfectly level or it crashes,

but at least it lands!!

Link to comment
Share on other sites

There are several reasons why you crash:

(1). Until you learn to land at '0 kts' turn off your crash detection.

(2). DON'T set your 'Realism' to 'Hard'. Set it to 'Medium' (and LEAVE IT THERE).

(3). Remove 'Type 5' (water rudder), lines 12 & 13 then copy past new floats (below). (ie: The rudders are 7.530 (vertical) and they are hitting before your floats).

(4). Increased crash tollerance to 3200, added steering (no need for water rudders).

 

point.14= 4.000, 5.242, 3.369, -4.543, 3200.0, 0.000, 0.519, 0.000, 0.100, 4.500, 1.000, 0.000, 0.000, 4.000, 0.000, 0.000

point.15= 4.000, -4.166, -3.369, -4.543, 3200.0, 0.000, 0.519, 30.000, 0.100, 4.500, 1.000, 0.000, 0.000, 4.000, 0.000, 0.000

point.16= 4.000, -4.166, 3.369, -4.543, 3200.0, 0.000, 0.519, 30.000, 0.100, 4.500, 1.000, 0.000, 0.000, 4.000, 0.000, 0.000

point.17= 4.000, 5.242, -3.369, -4.543, 3200.0, 0.000, 0.519, 0.000, 0.100, 4.500, 1.000, 0.000, 0.000, 4.000, 0.000, 0.000

 

Now you shouldn't crash even if landing at 40 kts! (not recommended). Check back.

Chuck B

Napamule

i7 2600K @ 3.4 Ghz (Turbo-Boost to 3.877 Ghz), Asus P8H67 Pro, Super Talent 8 Gb DDR3/1333 Dual Channel, XFX Radeon R7-360B 2Gb DDR5, Corsair 650 W PSU, Dell 23 in (2048x1152), Windows7 Pro 64 bit, MS Sidewinder Precision 2 Joy, Logitech K-360 wireless KB & Mouse, Targus PAUK10U USB Keypad for Throttle (F1 to F4)/Spoiler/Tailhook/Wing Fold/Pitch Trim/Parking Brake/Snap to 2D Panel/View Change. Installed on 250 Gb (D:). FS9 and FSX Acceleration (locked at 30 FPS).
Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...