Ff you could have one thing in the next update it would be…
-
Thank you, everyone! i got it ! the “UHF-BUP” is “UHF Back-up”.
I was confused about “UHF-BUP” before!:p
-
Throttle CUTOFF/IDLE movement animation (or at least position changes like switches do).
When g_bUseAnalogIdleCutoff = 0, Startup an engine without advancing throttle half than click idle detent position.Reasons:
-
Using Cougar throttle CUTOFF detent may accidentally cutoff engine while in the air.
-
Using Cougar throttle CUTOFF detent also limits IDLE to MIL range to 1/3 length of the whole throttle movement.
It is just as same length as MIL to MAX AB or CUTOFF to IDLE.
-
Non-Cougar throttle user studies wrong about F-16 startup procedure.
-
Warthog user can start up/shut down the engine by simply moving their throttle from/to CUTOFF position to/from IDLE without using troublesome TARGET software.
-
-
The pilot body/ legs only mod as an option for all Viper-versions. Please
-
Throttle CUTOFF/IDLE movement animation (or at least position changes like switches do).
When g_bUseAnalogIdleCutoff = 0, Startup an engine without advancing throttle half than click idle detent position.Reasons:
-
Using Cougar throttle CUTOFF detent may accidentally cutoff engine while in the air.
-
Using Cougar throttle CUTOFF detent also limits IDLE to MIL range to 1/3 length of the whole throttle movement.
It is just as same length as MIL to MAX AB or CUTOFF to IDLE.
-
Non-Cougar throttle user studies wrong about F-16 startup procedure.
-
Warthog user can start up/shut down the engine by simply moving their throttle from/to CUTOFF position to/from IDLE without using troublesome TARGET software.
Well, you know reason one is a feature, not a bug.
2 - no, it doesnt.
3 the cutoff detent setup works just fine regardless of throttle you use.
-
-
new weapons AMM120D, AGM53
asa radar -
Well, you know reason one is a feature, not a bug.
2 - no, it doesnt.
3 the cutoff detent setup works just fine regardless of throttle you use.
2.Are you sure?
3.When g_bUseAnalogIdleCutoff = 0, the current procedure is “advance the throttle from IDLE to half of MIL than click cutoff detent which is now becoming “root of the throttle” after advancing it than back it to IDLE”
When g_bUseAnalogIdleCutoff = 1, the cutoff detent setup works just fine regardless of throttle you use, but I am not talking about that at 3.
I am not sure any other joystick other than Cougar that has a mechanical detent and axis detection between CUTOFF to IDLE. Maybe Saitek does?
Warthog has mechanical detent but no axis. Most of the joystick doesn’t. So disabling g_bUseAnalogIdleCutoff = 0 should be more common.
Even for Cougar user those bump can be easily go across from IDLE to CUTOFF while flying.
So unless you are using RL F-16 throttle rail for your home pit, I guess not so many of Cougar user enables g_bUseAnalogIdleCutoff = 1. -
When g_bUseAnalogIdleCutoff = 1, the cutoff detent setup works just fine regardless of throttle you use, but I am not talking about that at 3.
I am not sure any other joystick other than Cougar that has a mechanical detent and axis detection between CUTOFF to IDLE. Maybe Saitek does?
Warthog has mechanical detent but no axis. Most of the joystick doesn’t. So disabling g_bUseAnalogIdleCutoff = 0 should be more common.
Even for Cougar user those bump can be easily go across from IDLE to CUTOFF while flying.
So unless you are using RL F-16 throttle rail for your home pit, I guess not so many of Cougar user enables g_bUseAnalogIdleCutoff = 1.Saitek joysticks, and basically most joysticks which use a detent.
I cant speak for all Cougar users, but I only wish I had a real throttle rail, and I use the analogue idle cutoff.
Using Cougar throttle CUTOFF detent also limits IDLE to MIL range to 1/3 length of the whole throttle movement.
It is just as same length as MIL to MAX AB or CUTOFF to IDLE.
Very sure. You can adjust the position of those detents - physically on the Cougar, by disassembling the throttle and adjusting the position of the detent rings, and digitally in the BMS software,
by RTFMby moving the throttle axis to the position desired for a detent, then left clicking to set the position of the AB detent, and right clicking to set the position of the IDLE detent.My IDLE to MIL range in BMS is over 90% of the raw data value range supplied by the cougar hardware, with the MIL to AB and the OFF to IDLE ranges combined taking up less than 10% of the total digital travel. They take up a little more of the physical travel, as the raw data values of the throttle axis dont seem to match up perfectly with the hardware travel.
As for point 3… I did think you were talking about the analogue cutoff. Its been a long time since I used the default shitty cutoff mode, but I dont seem to recall what you describe. You are saying that the IDLE position becomes the location of the throttle when you click the cutoff detent, but this is not what I recall happening. I recall that if you do not immediately retract the throttle after clicking the detent, the aircraft will rapidly rise above idle RPMs. So perhaps one of us is misunderstanding the way it works, or perhaps Ive misunderstood what you are saying?
shrugs
-
Delayed acquisition time for enemy fighter pilots.
As it is now, enemy fighter pilots can acquire and lock you as soon as you enter their field of view or their radar cone, which makes them react way faster than a reasonably lucky human pilot.
The same is true for MANPADS carriers. -
Very sure. You can adjust the position of those detents - physically on the Cougar, by disassembling the throttle and adjusting the position of the detent rings, and digitally in the BMS software,
by RTFMby moving the throttle axis to the position desired for a detent, then left clicking to set the position of the AB detent, and right clicking to set the position of the IDLE detent.Oh, I was forgetting about detent rings. I removed bump base because I don’t want them as they are too loose to use as a idle detent, but too noisy while moving throttle between IDLE to MIL.
However removing bump base also removes AB detent. I have to reinstall them and try adjusting detent rings again. Thanks.As for point 3… I did think you were talking about the analogue cutoff. Its been a long time since I used the default shitty cutoff mode, but I dont seem to recall what you describe. You are saying that the IDLE position becomes the location of the throttle when you click the cutoff detent, but this is not what I recall happening. I recall that if you do not immediately retract the throttle after clicking the detent, the aircraft will rapidly rise above idle RPMs. So perhaps one of us is misunderstanding the way it works, or perhaps Ive misunderstood what you are saying?
When starting up the engine you forward throttle from the IDLE, click the idle detent, then retract the throttle to IDLE.
Idle detent clickable position is just on the actual idle detent of the 3d model of throttle when they are on IDLE position, but it wil be on the root of the throttle after we forward them,
So while in engine start up procedure in falcon, we click throttle itself. -
An option to clear all PPT without resetting the whole data cartridge.
-
An option to clear all PPT without resetting the whole data cartridge.
I think WDP planner can do this. Failing that, one can always do it manually just by editing the .ini file.
-
Fix the ICP GPS data entry bug
When manually entering a GPS coordinate (say for a target) when in the cockpit, the least significant digit will be off by one. This is not a problem when the coordinates are entered in 2D via the DTC. The work around is to enter the LSD as one value higher than you want.
My mate Cham and I verified this in multiplayer together
-
This post is deleted! -
Fix the ICP GPS data entry bug
When manually entering a GPS coordinate (say for a target) when in the cockpit, the least significant digit will be off by one. This is not a problem when the coordinates are entered in 2D via the DTC. The work around is to enter the LSD as one value higher than you want.
My mate Cham and I verified this in multiplayer together
Civilian aviation GPS (i.e. GNS430 and 530) does the same. May be it’s a feature and not a bug?
-
Civilian aviation GPS (i.e. GNS430 and 530) does the same. May be it’s a feature and not a bug?
Cant imagine why it would be like that in RL modern GPS, even if the Viper doesnt behave this way. Would like to know why.
-
Improve the simulation of carrier landing. Add the ATC’ radio list for aircraft carrier’s BRC when approach.
-
Improve the simulation of carrier landing. Add the ATC’ radio list for aircraft carrier’s BRC when approach.
that’s a good one i like the idea
-
What I mean is that the aircraft never despawns like ground units.
The proper software term is persistance.
Aircraft should be persistant in the campaign world.Each aircraft if received battle damage would be in maintenence needs day before you can ride again depending on damage.
More minutes on older frames increases likelyhood of random failures.
This would make flying in Campaigns even more immersive and fun. Right now losing a plane almost has no consequences landing like a fool or rolling around in grass no consequences.
If you have your settings on realistic there should be consequence and reward for flying accurate. Even small bonuses for proper use of taxiways and ATC. ETC…
Small things like that slowly added on to the campaign would really put it in the next tier of fun for campaigns. -
Cant imagine why it would be like that in RL modern GPS, even if the Viper doesnt behave this way. Would like to know why.
At 3 digits behind the decimal, the accuracy is roughly 1m. For civil use, that’s more than precise enough, so it doesn’t really matter if you’re 1 or even a few digits off. For military purposes, however, that 1 meter difference could mean the difference between the JDAM blasting through the window or hitting the wall.
-
What I mean is that the aircraft never despawns like ground units.
The proper software term is persistance.
Aircraft should be persistant in the campaign world.Each aircraft if received battle damage would be in maintenence needs day before you can ride again depending on damage.
More minutes on older frames increases likelyhood of random failures.
This would make flying in Campaigns even more immersive and fun. Right now losing a plane almost has no consequences landing like a fool or rolling around in grass no consequences.
If you have your settings on realistic there should be consequence and reward for flying accurate. Even small bonuses for proper use of taxiways and ATC. ETC…
Small things like that slowly added on to the campaign would really put it in the next tier of fun for campaigns.–----------------------------------------------------------------------------
I agree with that idea. Add random failures in the campaign. The probability of failures occuring should be dependent on supplies and fatigue.