Frederf

LOSE cue (not lost) is indication by MMC that missile will not impact target due to battery, kinematics, or missile seeker angle. A missile in a LOSE state is projected not to impact if things keep going the way they're going. The situation can change to turn a lose into a win.

I kind of agree but I don't see what you mean specifically. Ultimately the input has to return to zero if the cyclic is going to stay at the center of the artificial feel middle. If you could express your idea mathematically I could think about it better.

I can get it to work normally but I also see your issue and can demonstrate a few others myself. In your track it appears that the solution was just about to come onto the HUD at the moment of pickle which may play a part. Some visual oddities noted: heading tape not hidden Slant range readout is not accurate bank angle scale not hidden lack of PUAC Major functional oddities: ASL does not provide steering pipper dot does not remain on the designated point turning away after designation results in release early release in some situations release of second bomb in some situations It's like there's an auto-release whenever it senses you're getting farther from solution. One should be able to designate and then turn 360 degrees in a circle before driving in to release.

Realize that the Apache stick doesn't center when the trim button is pressed. If it was 25% deflected and trimmed, it's still 25% deflected. It is our simple spring joysticks which don't behave properly. If input was +0.1 and then trim is pressed, what happens? With instant you get 0.1 as the new center and instant +0.1 for 0.2 total. With freeze the input isn't added until it returns to (essentially) 0. At some point the position of the cyclic has to be a different relationship to input after trim compared to before time. I think the lock-and-window type scheme is unacceptable that it prevents any control input until you hit a window. Instant has an unfortunate upset where the relationship is changed suddenly but the user is still in control. The old Ka-50 method of a time-based blended transition was a better version of instant. I think there could be a better version with blending that was smart, based on how the user was moving the stick back to neutral instead of a "blind" blending based on time.

There was a Cosmo video just recently that covered LMC. There was no mention of anything wrong just that practice is needed.

The F-16 doesn't have a GPU. It has a pneumatic accumulator (two actually) backing hydraulic pressure to the JFS. The JFS is a fuel-burning device that spins up the main engine via the gearbox. There is only one way to start the F-16 in DCS, via the brake/JFS accumulator(s). If you just want ground electrical power, then just ask for ground power. Ground electrical power integration is automatic and powers the airplane in the same way the main engine generator does. Right now the TGP doesn't work with ground electrical power (think that's a bug) but everything else is A-OK. I don't know if it's possible to configure the airplane on ground power and then start and fly. It's not done in reality. They either are on a cold jet alert or with engines running. There's no electrical on/engine off alert that I know of. The DTC makes the launch process quite fast if needed. If even those 2 minute response times isn't enough they would run the engine possibly with ground hot refueling as needed. Looks like the FCR won't turn on on ground power either (might be a bug). Anyway, you can sit on ground power and do almost anything to get ready then start engines and go. I didn't see any issue apart from the FCR/TGP (maybe HTS too didn't test).

The laser updates the position only so long as the laser is currently firing. If you laser while making a mark point and then bomb the mark point then it doesn't matter if you lase during release. If you're dropping on a "live SPI" from TGP then you need the good target data on pickle press while the target is downloaded into the bomb and released.

Under marginal release conditions the bombs fail to fly well to their set destinations and can come up 100s of meters short. There is also possible target location error when using onboard sensors (especially visual). When testing bomb performance it's important to use the most "direct coordinates" form of targeting to separate those other effects. In the F-16 that would be a steerpoint destination without TGP or FCR sensor aiming. Visual aiming I wouldn't even consider as a basis for weapon accuracy performance. DCS does model the difference in performance with and without GPS. The GPS acquire time I dunno but it's true real JDAMs get more accurate the long they're in the air to a point. JDAMs will never be through the tank commander's hatch accurate or repeatable in any case but in the best situation they can absolutely kill an MBT with a very high Pk.

I hope not. A lot of aircraft had what amounts of a DTC in practice even if it wasn't an actual cartridge. The concept of configuration of aircraft for the mission or operator preference distinct from factory condition is much wider than data cartridges. The rudder trim tab bend angle on a WWI biplane would be a "data cartridge" type detail.

In the Cessna it was how the radio changes were done. Rotate the knobs to adjust the standby freq then the flip-flop button to exchange the standby and active. The only way to change the primary was to flop in a standby. Because it was a knob and not a type-it-in you couldn't instantly change over if you were altering the primary directly. The absolutely most significant benefit is the ability to plan ahead. You set your radios in the future whenever you could. Especially with someone else to help you they'd be dialing in the frequency as the controller told it to you or as needed. The Apache can do either direct or swap adjustment based on a setting on the COM MPD page. I'm looking forward to setting it on standby tune mode.

It's any key 1-9. The M3 MLU doc has the same page but it's missing the T feature so I'm guessing it's newer. My guess is either "T" targeting data from or transmitting something to that STN. The other guess is Team Leader. I notice when you change your ownship STL (#1, #2, #3, etc.) the T auto-follows erasing the T on the old ownship and appearing on the new ownship without changing any others. I don't know what multiple team leaders would mean. Maybe if 1 and 5 had a "T" then it assumes 2-3 are members of 1's team and 6-8 are members of 5's.

LMC on-and-slew utility seems very sensitive to the particular logic in the system. Usable vs unusable could be a few values in the logic. Considering that a common nickname for the manual tracking switch is "force controller" I'm guessing it's a zero-displacement force transducer based device so going from any input to zero would be much faster than a displacement joystick.

The caution persists until reset. It's a sort of electrical system master caution. It does auto reset sometimes. It's possible to start under BATT but normally it's under MAIN PWR. BATT is used to test the FLCS latching feature (that it doesn't) before start.

LMC is great when engaged with no tracking input, useful when engaged while tracking, and completely impossible when applying input after it's already on. I don't know what technique is appropriate when introducing slew input with LMC on if any exists.

I don't know how flexible the Apache is on number of digits. I know it will take 8 but not 10. I could see it taing six but if not then padding 123456 should be done like 123x456x to add a least significant digit to the easting and northing.

Power lever can move past open spider handle when moved by keyboard inputs. Apologies for the similar report but as pointed out the difference in axis and keyboard input behavior is explained by the axis behavior being correct and the keyboard behavior being wrong. F-16 Throttle AB axis cold.trk

It wouldn't matter. "Hey, Singapore does..." "We're modeling a USAF airplane so irrelevant."

Doesn't matter, with PN navigation the target can be doing 1,000mph as long as the LOS rate is zero.

Well then the bug is that keyboard control can. I'm not changing anything except keyboard or axis control.

The DCS model doesn't seem to source time from GPS when available at all and I would treat it as such. You can't see GPS time directly afaik. You would see GPS time indirectly when system time synced with it. Time should be manual without GPS and auto with. It would make the most sense for system time to start a random time in the past say 2-23 hours ago. The idea that the airplane was shutdown 1 sec before you strapped in is weird. When MMC comes online it would initialize to GPS source and quickly sync if possible. I don't know if the avionics GPS switch off inhibits GPS time use but probably. Time can be changed to manual either normal or hack and back onto auto at any time. GPS weapons shouldn't care either way.

Oddly AI JTAC doesn't give full coord. That PB645283 looks like Nevada so it's probably 11S PB 645283. Apache is happy to take MGRS without the spaces. Unless you're unlucky to be right on the edge between two UTM zones you can assume JTAC's target is in the same zone (and lettered grid) as JTAC and probably you as well. It might be easier to throw down a quick target point off TADS and then edit its coordinate. The system helpfully puts the KU cursor at the beginning of the numbers to quickly edit those. If it insists on an 8 digit grid then just add zeroes (or 5) after the 3rd and 6th digits to pad it out. A 6-digit MGRS is good to a 100x100m box precision.

Yup, pull the COM1 or COM2 UFC selector knob to bring up the menu and then select (colonize) the GRCV option. That will monitor 243 (and maybe 121.5?) internal to DCS and you should see a "G" at the end of your frequency in the SRS overlay indicating guard reception there.

Dynamically spawning aircraft from an airbase pool is an understandable idea. Most MP servers operate this way. DCS at its core is designed as more rigid scenario. It's a whole different way of thinking. The mission planner (MP) being available in multiplayer has long been a desired feature. Lots of things are only really possible with the MP like an Su-25T's flight plan or some airplanes' radio presets or any callsign for instance. It wouldn't be too much of a stretch to include the ability to generate an entirely new flight/group in the MP (single or multiplayer) the same way one does in the ME. Only the warehouse supply would be locked. That would be change #1. Change #2 would be to the slot join UI which as far as I can tell now is semi-static based on the mission. I don't think the list can change based on runtime events. Personally, I don't think the slot join UI should be purely a list like it is currently. An F10-like map location based initial selection geographically similar to the IL-2 Sturmovik series is more friendly. The type of mission of "spawn any plane out of the pile anywhere at any time" is not well served by the current system.

When the airplane is off the power lever cannot be increased beyond MIL position by axis control. Keyboard control is unaffected. Detent operation was tested with detent toggled on (off) inhibiting (not inhibiting) keyboard control as expected. Checked without mods. Track demonstrates: Keyboard motion through full range Keyboard motion halted by detent on Keyboard motion through full range (to show detent has been toggled off) Joystick motion halted at MIL Power lever motion when the airplane is started by axis is unaffected. Note: If detent is toggled on while power lever is in the afterburner range the keyboard command to increase throttle results in the power lever position reset behind the detent and axis control is the same. Probably when detent is in motion should be unaffected within the afterburner range as well as motion from afterburner range to idle-mil range. Only crossing the threshold from MIL to afterburner range should be inhibited. F-16 Throttle AB axis cold.trk

Theoretically the trim could initialize based on the ME data based on some kind of tabulated data. The MiG-21 is particularly bad because its default trim state is a 0g ballistic path which will flame out the engine quickly if not corrected.