Flanker251 Posted November 17, 2018 Share Posted November 17, 2018 Hi, simmers. The wonderful freeware F-35B from Dino Cattaneo is working okay in P3D (v3) however I have two problems with it: 1. I can't find an APPROACH or ILS mode, only a VOR/LOC.... 2. When landing the F-35B aircraft in a 'normal manner' (no VSTOL) on an airfield strip, 99 out of 100 times the plane crashes in P3D when I have full realism on. I tried different speeds and different flaps settings as well as enabling or disabling the Flight Director. (also tried with landing gear down ;)) Anyone can help me out with suggestion to land this F-35B in P3D with realism enabled. Any directions to solve mentioned problems are very welcome, so thanks in advance! Link to comment Share on other sites More sharing options...
mallcott Posted November 18, 2018 Share Posted November 18, 2018 Hi, simmers. The wonderful freeware F-35B from Dino Cattaneo is working okay in P3D (v3) however I have two problems with it: 1. I can't find an APPROACH or ILS mode, only a VOR/LOC.... 2. When landing the F-35B aircraft in a 'normal manner' (no VSTOL) on an airfield strip, 99 out of 100 times the plane crashes in P3D when I have full realism on. I tried different speeds and different flaps settings as well as enabling or disabling the Flight Director. (also tried with landing gear down ;)) Anyone can help me out with suggestion to land this F-35B in P3D with realism enabled. Any directions to solve mentioned problems are very welcome, so thanks in advance! Good as the freeware is, READ the instructions - it was designed for FSXA, P3Dv1 and P3Dv2 and NOT P3dV3 (or v4) it has been superceded by the payware which corrects faults in a number of areas and is now at version 3.53 (freeware at 2.41 IIRC): CHANGE LOG Version 3.53 - 02/11/2018 - Fixed major bug in NAV1/TACAN frequency conversion causing generating incorrect TACAN channels in some instances. - Fixed bug preventing NAV1 frequency tuning once a TACAN channel has been entered - Fixed graphic glitch in MFD TSD1 screen - Fixed minor graphic glitch in BFI Baro setting window - Updated Koninklijke Luchtmacht F-35A livery - Added F-35C VFA-147 Argonauts USN livery - Fixed wrong entry in F-35C configuration file Link to comment Share on other sites More sharing options...
Flanker251 Posted November 18, 2018 Author Share Posted November 18, 2018 Thank you for your reply malcott. Still... the F-35A shipped with P3Dv3I can't find there also neither an ILS or APPROACH mode. Also I have the same problem to land the F35A (shipped with P3Dv3), with realism on in the sim 99 out of 100 times the plane crashes, while all other planes I can set safe to the ground.... Sadly my question for help thus is still open... will however read manual again again. Link to comment Share on other sites More sharing options...
mallcott Posted November 18, 2018 Share Posted November 18, 2018 Thank you for your reply malcott. Still... the F-35A shipped with P3Dv3I can't find there also neither an ILS or APPROACH mode. Also I have the same problem to land the F35A (shipped with P3Dv3), with realism on in the sim 99 out of 100 times the plane crashes, while all other planes I can set safe to the ground.... Sadly my question for help thus is still open... will however read manual again again. I had no idea you were talking about the F-35 that shipped with P3Dv3 - you clearly alluded to `freeware`in your original post, which implies a download. There is no auto approach system in the P3Dv3 version. That's why the payware version exists. Link to comment Share on other sites More sharing options...
Flanker251 Posted November 18, 2018 Author Share Posted November 18, 2018 A reply to myself? Looks like a blog. Anyway: I read the manual again of the freeware F-35 package, learned nothing much concerning conventional landing, only about VTOL, STOL and carrier landings (will be my next targets for F-35). In the mean-time, after much trial and more errors I found out this: Percentage of successful landings is increasing in P3Dv3 with realism settings high. 1. Flaps at 45º when landing. 2. Very gradually diminish speed with Auto-Throttle on, just before touching tarmac have a speed of ca. 130 knots. 3. Only release auto-speed when touch-down has occured. 4. Diminish engine-power (F2 or F1) and gently use the brakes. Oh, and there's something with the HUD indication, but I can't yet lay my finger on that. In the mean time I hope some people still can respond to my post.... Many thanks in advance for replying. Link to comment Share on other sites More sharing options...
rcbarend Posted November 18, 2018 Share Posted November 18, 2018 Not sure if this specific for P3Dv3 (for which this freeware release was not designed or supported), but what you can try: 1. Lose a lot of weight (fuel or payload) before landing. So try it with minimal fuel and payload,to exclude that the crashing is caused by overweight at landing. 2. Strengthen the nosewheel in the contactpoints section of the aircraft.cfg's point.0=1, -18.00, 0.00, -6.65, 1000, 0, 0.96, etc …. Change "1000" into "1600" (like for the main wheels) Rob Link to comment Share on other sites More sharing options...
napamule2 Posted November 19, 2018 Share Posted November 19, 2018 Pardon me, but '-18.000' for the 'Lon' of NOSE wheel? Sounds like it would be a tail dragger with that figure for 'Lon' (point.0=1, -18.00). And the 'Impact Damage Threshold' CAN be as much as 2999.00 with no ill effects and may help in that respect. Perhaps he should copy/paste the contact points for point.0 thru point.2 so we can maybe spot if there IS a problem there. 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 More sharing options...
rcbarend Posted November 19, 2018 Share Posted November 19, 2018 Pardon me, but '-18.000' for the 'Lon' of NOSE wheel? Sounds like it would be a tail dragger with that figure for 'Lon' (point.0=1, -18.00). Chuck B Napamule That's how Dino defined it. But given this in the aircraft.cfg: reference_datum_position = 29.00, 0, -2.5 empty_weight_CG_position = -30.00, 0, 0 the -18.0 makes sense. Not sure why the visual model datum point was defined in such a way, but it's nearly the same as in the default F/A18 in FSX-Acceleration. Rob Link to comment Share on other sites More sharing options...
Flanker251 Posted November 23, 2018 Author Share Posted November 23, 2018 Fisrt of all: Thank you. Is that what you did, Bob, nosewheel adjusting? I did crash many times before the nosewheel even did touch the tarmac... Link to comment Share on other sites More sharing options...
Flanker251 Posted November 23, 2018 Author Share Posted November 23, 2018 Hi npamule2, Contact point I did not alter IMHO: [contact_points] //0 Class //1 Longitudinal Position (feet) //2 Lateral Position (feet) //3 Vertical Position (feet) //4 Impact Damage Threshold (Feet Per Minute) //5 Brake Map (0=None, 1=Left, 2=Right) //6 Wheel Radius (feet) //7 Steer Angle (degrees) //8 Static Compression (feet) (0 if rigid) //9 Max/Static Compression Ratio //10 Damping Ratio (0=Undamped, 1=Critically Damped) //11 Extension Time (seconds) //12 Retraction Time (seconds) //13 Sound Type // TO MATCH 3D MODEL ;Gear point.0=1, -18.00, 0.00, -6.65, 1000, 0, 0.96, 75.0, 0.4000, 2.5, 0.200, 7.0, 7.0, 0, 0.0, 0.0 point.1=1, -37.50, -6.8, -6.85, 1600, 1, 1.43, 0.0, 0.53, 2.0, 0.2, 6.9, 6.9, 2, 0.0, 0.0 point.2=1, -37.50, 6.8, -6.85, 1600, 2, 1.43, 0.0, 0.53, 2.0, 0.2, 6.85 7.1, 3, 0.0, 0.0 ;Wingtips point.3=2, -40.7, -18.75, 1.25, 800, 0, 0.0000, 0.0, 0.0000, 0.0, 0.0000, 0.0, 0.0, 5, 0.0, 0.0 point.4=2, -40.7, 18.75, 1.25, 800, 0, 0.0000, 0.0, 0.0000, 0.0, 0.0000, 0.0, 0.0, 6, 0.0, 0.0 ;Bottom point.5=2, -9.43, 0.00, -1.9, 800, 0, 0.0000, 0.0, 0.0000, 0.0, 0.0000, 0.0, 0.0, 4, 0.0, 0.0 // Reference EOTS point.6=2, -45.00, 0.00, -2.7, 800, 0, 0.0000, 0.0, 0.0000, 0.0, 0.0000, 0.0, 0.0, 9, 0.0, 0.0 // Reference tailhook housing point.7=2, -30.00, -3.90, -2.8, 800, 0, 0.0000, 0.0, 0.0000, 0.0, 0.0000, 0.0, 0.0, 9, 0.0, 0.0 // Reference weapon bay/1 point.8=2, -30.00, 3.90, -2.8, 800, 0, 0.0000, 0.0, 0.0000, 0.0, 0.0000, 0.0, 0.0, 9, 0.0, 0.0 // Reference weapon bay/2 ;Top point.9=2, -14.50, 0.00, 4.85, 800, 0, 0.0000, 0.0, 0.0000, 0.0, 0.0000, 0.0, 0.0, 4, 0.0, 0.0 // Reference cockpit top point.10=2,-52.00, -7.80, 9.30, 800, 0, 0.0000, 0.0, 0.0000, 0.0, 0.0000, 0.0, 0.0, 9, 0.0, 0.0 // Reference empennage lt point.11=2,-52.00, 7.80, 9.30, 800, 0, 0.0000, 0.0, 0.0000, 0.0, 0.0000, 0.0, 0.0, 9, 0.0, 0.0 // Reference empennage rt static_pitch=1.00 static_cg_height = 9.0 gear_system_type=1 //Hydraulic emergency_extension_type=1 //None=0,Pump=1,Gravity=2 Link to comment Share on other sites More sharing options...
Flanker251 Posted November 23, 2018 Author Share Posted November 23, 2018 Hi malcott, I had he issues with both the freeware F35 package (which has F-35B) and the F35A shipped with P3Dv3.4.... I did not buy yet the payware version... Thank you for replying! Link to comment Share on other sites More sharing options...
Flanker251 Posted November 23, 2018 Author Share Posted November 23, 2018 Hi, all you responding to this post, Thank you for the input! While i was busy transmitting aircraft from FSX to P3D (now busy with POSKY 747), I did not check your replies here. I'm sorry. Still any help would be welcome. Link to comment Share on other sites More sharing options...
mallcott Posted November 24, 2018 Share Posted November 24, 2018 Hi, all you responding to this post, Thank you for the input! While i was busy transmitting aircraft from FSX to P3D (now busy with POSKY 747), I did not check your replies here. I'm sorry. Still any help would be welcome. Only use planes designed for P3D IN P3D. The latest version v4.3 is NOT designed for FSX aircraft, and uses a completely different installation method. You WILL corrupt the P3D installation pouring useless historic crap into it. POSKY 747 does NOT work in P3Dv4. More research needed. Link to comment Share on other sites More sharing options...
Flanker251 Posted November 24, 2018 Author Share Posted November 24, 2018 Hi malcott, I agree what you say about P3Dv4, on the other hand I'm talking about P3Dv3.4.... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.