Jestr

Hi! Could you offer some guidance on how modify the repo/package file so that when a user queries the repo, he sees a new version? e.g. mod version 1.0 already on repo I as admin, update the mod to 1.1 How do I edit the package/repo so that the user wont have to uninstall the old version, and then download the new version with a new version extension? Thanks!

There should be a caution though when the AP disengages ( i.e. can´t hold altitude or attitude). Currently this does not occur.

just to chip in - same here. Error code 502

Just want to bump this so that it is not forgotten to add black outlines. White on grey, especially in VR is really hard to see clearly. Black outlines make a world of difference!

DCS World Open Beta 2.8.0.33006 Bug: If you loose engine - either by shutting it off, running out of fuel or whatever, and subsequently EPU activates - the INS looses alignment and you loose all inertial reference in the HUD ( ADI remains fine). To reproduce: 1. Enter a turn ( e.g. 30° bank ) 2. Set throttle to Idle detent to shut it off 3. Notice the EPU automatically activate. 4. Notice HUD ladder mis-align. [ Expected result should be that INS integrity is maintained ] An engine-out should not trigger a total INS failure. Trackfile attached. Example (old) hud video from the 80's showing an actual engine-out. epu_ins.trk

This is still broken following the update to SEC in latest DCS version. SEC is essentially useless until this is fixed.

Deffinetly looking forward to using this, good effort! I opened up a feature request - hoping that the app will allow blank ( separator) steerpoints, so that they dont always have to be sequential. This is useful when drawing boundaries for example, using steerpoints. Would also be useful later on when the F16 has the proper waypoint set for lines 1-4 etc.

Ok so what I had to do was to grab the unitID´s from the ME then create a Avionics\F-16C_50\<unitID>\UHF_RADIO\SETTINGS.lua for each aircraft, then copy and paste a working SETTINGS.lua into each folder. Abit tedious, but it works. Manipulating the presets in the ME ( radio list for the F16) appears to do nothing - A10´s will still overwrite those apparantly.

Ok, so I figured it out. Have to use prepare-mission for each available F16 in the mission. This will generate Avionics\F-16C_50\166\UHF_RADIO\SETTINGS.lua and Avionics\F-16C_50\166\VHF_RADIO\SETTINGS.lua - 166 being the aircraft ID. This is going to be fun for some 20-30 aircraft.... Is there any way to access said aircraft ID´s ? They are not shown in the ME...

Re-saving and re running prepare mission appears to create the relevant files within the miz: Avionics\F-16C_50\166\UHF_RADIO\SETTINGS.lua and Avionics\F-16C_50\166\VHF_RADIO\SETTINGS.lua however changes made in the editor presets do not seem to propagate to these files. Here is a link to a quick re-play if that helps. All the F-16 have the same presets in the mission editor - case in point - UHF preset 2 should be 237. https://drive.google.com/file/d/1pyeJRxrdALAOhqrvW7pmrDqv3ky1rjRY/view?usp=sharing Any idea whats going on?

Does saving old missions not work? Does the mission have to be "made from scratch" so to speak?

I might be being obtuse, but I can´t get this to to work. I have a multiplayer mission ( that I´m testing locally) with a bunch of F16 presets as well as A10C II´s present, but no matter whether I save the mission, or use the prepare mission function within the editor, the presets in the F16 always appear to be overwritten. What is the best way to convert an old mission?

To pile on this: to clarify what OPs intention is ( probably ) - at least as far as I see it - and would love to see implemented: When you press PTT for VHF or UHF, have a secondary function that does NOT open in game communication menus, but does all the other things - such as highlighting the UHF or VHF ( inverse video black ) on the DED. This allows users of whatever 3rd party communications application they may be using to map the same keys to UHF and VHF transmit to the application, as well as the DCS F16 control mapping for the radios - without actually opening the communication menu as if one was about to talk to the AI. In short - provide a control mapping called "VHF Transmit - PTT only" that does absolutely nothing but highlight the VHF radio, then do the same for UHF. ( and inhibit a datalink round if using the IDM?).

Page 36: In NORM, the AL pointer indicates remaining fuel in the aft left reservoir and the A-1 fuselage tank, and the FR pointer indicates the sum fuel in the forward right reservoir tank and the F-1 and F-2 fuselage tanks. Might want to add this note: The FUEL QTY SEL knob must be in NORM for operation of the automatic forward fuel transfer system, trapped fuel warning, and for the BINGO fuel warning computation to be based on fuselage fuel. Tested this in DCS and it is implemented correctly apparently.

Whoa, good catch. Had not thought of this, precision mode was indeed on (FSSB R3L). Thanks!

DCS 2.7.2.7910.1 Open Beta Pulling stage one trigger in any master mode seems to trigger what appears to be something like the A10 gun stabilization. This has quite negative consequences during say BFM, when the FLCS gains appeared to be halved, or when you´re just trying to fly an orbit and manually lasing. The gun compensation on the F16 should only activate when firing and should not have any effect on the FLCS gains. According to the -1: GUN COMPENSATION The FLCS automatically compensates for the off-center gun and the aerodynamic effects of gun gas emissions during firing by moving the flaperons and rudder. Gun compensation is optimized for 0.7-0.9 mach range; therefore, all excursions may not be eliminated. For example, gunfiring at low mach may result in nose left excursions while nose right excursions are likely at higher mach. Failure monitoring of gun compensation circuits is not provided and there are no caution light indications for incorrect compensation. To reproduce - instant action - freeflight - any theater. Initiate a turn either to the left or right at a set G ( for example 5G) and hold. Pull trigger to 1st detent while holding same force on the stick. Expected behaviour: G remains constant. Actual behaviour: G is ~halved - roll input it less sensitive ( feels like landing gains ). Here is the track: https://drive.google.com/file/d/1eC3Kb8NSzLjj2CgS-msdFbG_mD3l692r/view?usp=sharing

Also reported here:

Could not find a solid report of this before, so apologies if this is a repost. I realize all this is WIP but the bug report rules said engine operations are fair game for reports Open Beta 2.7.1.6430 - instant action - cold & dark - caucuses The SEC implementation appears to be broken. When doing a SEC check on ground, the RPM drops ~10%, however snapping the throttle to MIL and back before RPM hits 85% is impossible since the RPM hardly rises at all. Extended stay in MIL causes FTIT to peg at 1200 before RPM drops below 60% and you loose the main generator. Retarding the throttle will bring the engine back to normal and the main generator back online. Reproduce: Start the engine normally. Enter SEC mode. Advance throttle to MIL and snap it back to idle before RPM hits 85% | or advance throttle to MIL and leave it there. Expected behaviour: SEC caution light - On [ ok ] RPM - Stabilized [ ok ] RPM may drop up to 10% from PRI value before stabilizing. Stabilized SEC idle rpm may be up to 5% lower then that in PRI [ ok ] Throttle - Snap to MIL and then snap to IDLE when rpm reaches 85%. Check for normal indications and smooth operations [ Fail ]. Actual results: Engine rpm does not increase. FTIT runaway ( would probably be a catastrophic engine failiure/fire ). RPM decreases below 60%. Main generator dies. NOZ POS - 10 % or less within 30 seconds after selecting SEC [ Fail ] Actual results: remains pegged at 0%. Track file ( showing only the above scenario ). https://drive.google.com/file/d/1dkAxWVgEXsKfZxjhwjN1VQqqRzaZDl9b/view?usp=sharing

Get rid of DCS-export if you´re using it, caused a crash with the TGP. Also caused a crash accessing P3 on the DED-Link16 page.

Was the track looked at before this was marked correct as is? TWS seems like it's broken as is. Cannot promote other tracks to system tracks with TMS up...

Tested in PG map. Fly towards two Tu-160´s spaced 1nm apart at 30.000. Set 80nm scope, RWS, A6, 4B - Note both aircraft visible on scope. TMS right long - enter TWS. 1. Wait for track files to generate ( note altitude numbers are superimosed on leader lines, making them impossible to read). 2. TMS right several times, note TWS jumps between the two tracks as expected. 3. TMS aft long to RWS again, then TMS right long again to enter TWS. Instead of TMS right to jump between tracks, TMS-UP short to bug a target. Note target hollows out. You can now no longer bug the other guy with a TMS UP short nor TMS right short to jump between tracks. Only way to reset is to TMS aft long back to RWS, then follow steps 1 and 2. Expected behaviour: TMS-up short should bug target under cursor or STT if cursor already over bugged target. Track file included. tws_strangenessr.trk

Hmm - maybe its because UHF/VHF is mapped to SRS and not UHF/VHF transmit in dcs ;) Can't have both though, lest I be bringing up the comm menus all the time :/

Not entirely sure this is implemented in tape your modeling but a pilot should be able to return to the previous frequency he was on, for example by pressing COM1-ENTER on the ICP. Implementing this would facilitate better/quicker channel hopping when you can anticipate what the next channel is that you're going to be on, effectively cocking the next frequency you're going to be on. Granted its quick and easy when it's just a single digit channel number, but saves some seconds when its manual frequencies. Example; You're on Channel 1 and you know that following line up, you're going to be checking in on 250.10 ( departure for example ) then after that you're pushing strike on channel 5. So being the good wingman - anticipating this, you press COM1-2510-Enter, then quickly again COM1-enter ( back on channel 2 ). You line up on the runway, hear lead say "push 250.10" - all you have to do is press COM1-enter...

Hello :-) Are there plans to implement this? When UHF / VHF is transmitting ( PTT held ) the DED label should highlight.

Indeed. According to AFI11-2F16V3 the max crosswind component for formation takeoff's is 15 knots. I'd be interested in seeing a trackfile of a fmn takeoff in those conditions now :-)