Jump to content

Recommended Posts

Posted

I noticed on the release version on v1.5 that it is difficult to taxi in the Mirage. It is either not getting enough power and slows to a stop, or too much and accelerates very quickly. I observed via externals that it appears there is a "sweet spot" where up to a certain RPM threshold ther engine does not generate any thrust but then when you cross the threshold a lot of thrust occurs so you have to constantly fiddle with the throttle.

 

I tested it out on the v2.0 install and it does not appear to have the same problem.

 

Is anyone else seeing this?

--Maulkin

 

 

Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars

Posted

Interesting, I noticed this on NTTR after the last 2.0 update. Perhaps it's dependent on weather settings or something like that? Haven't tried it on the most recent 1.5 as I'm mostly using the Tiger II and Gazelle at the moment given the recent Mirage issues.

 

If I remember correctly, it was about 61% RPM for me - just over that and I'd find myself accelerating up to 60, maybe even 80 knots (didn't really let it go), and just a smidge below 61% RPM it'd pretty much stop on its own.

Posted

Same ovservation here, hard to find a sweet spot to move constantly in an acceptable speed while taxiing. Like some imbalance of ground friction vs thrust produced. Not really anoying but I as well have to ride the throttle to keep it moving as I want her to move on a taxiway.

[sIGPIC][/sIGPIC]my rig specs: i7-4790K CPU 4.50GHz, 32GB RAM, 64bit WIN10, NVidia GeForce GTX 980 Ti, SSD+

 

A10C, UH-1H, M2C, F5E, Gazelle, KA 50, F18C, DCS 2.5x OB

Posted

Honestly I don't think it is ground resistance based on listening to the engine and watching the engine-blur behind the aircraft. I can hear and see the thrust "jumping" when I cross this hidden threshold. I will try testing more to see if I can nail it down.

--Maulkin

 

 

Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars

Posted

It's exactly 60%. In the range of 50-59% (F2 info bar) the steady state roll speed is 9 km/h (20% fuel, empty plane, aka lightweight). At 60% the steady state roll is in excess of 200 km/h.

 

Deceleration at no thrust (100km/h and then turn off engine) still seems too high but the majority of difficulty in taxiing at 20 km/hr is because the engine has a huge step in thrust between 59% and 60%.

Posted

I confirm Fredref's results. The threshold is 60%. I have attached the mission file I have been using to test this.

M-2000C cold start.miz

--Maulkin

 

 

Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars

Posted

Same thing happens in 1.5 as well, it is quite difficult to taxi with a constant speed, this has started happening a couple of updates ago

Posted

I would have expect RAZBAM's M-2000C to have the same taxi behaviour than ED's A-10C. There's no inertia "feeling" currently with the M-2000C, it just feels sticky on the ground meanwhile the A-10C has a really nice behaviour on the ground, those who owns it will probably get it. Fun thing is that the aircraft sometimes moves alone while idle and parking brake is set. This is witchcraft !

[sIGPIC][/sIGPIC]

  • Recently Browsing   0 members

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