Fresh

@Rudel_chw Hi Eduardo, sorry, I didn't realise you didn't approve of your mission/tutorial files being upleaded to the user section. Sincere apologies. I have deleted the file from the user section. This will also avoid confusion when 1.2 comes out.. Sincerely, Fresh

Hey, try displaying the control indicator overlay and checking that no controls are deflected by accident by another axis, e.g. left throttle also bind to rudder, or some button also adding right rudder trim whilst e.g. trimming nose up etc.

There's a comment about pilot body in the "known bugs" on initial release.. I'll post it in a sec.. It is not exactly what you described, but I guess the pilot body movements are still WIP...

I fully agree with this... please add your commets to my wish-list post:

Hi there, please have a look at the keybindings, at the moment it is very inconsistent: some switches toggle irrespective if I click left or right mouse button. Even some three way switches toggle through the three states with any mouse click. Also some dials I can mouse drag them (e.g. when setting the altimeter) and that works fine in 2D and in VR (I have mouse disabled in VR, and use my head movements as a mouse controller), however other dials, like the lighting don't work with click and drag in VR when using head movement. To summarise my wish: 1. All switches that go down, should be left click 2. All switches that go up, should be right click. 3. Rotary switches, like the fuel tank selector: left-click should turn it anti-clockwise, right-click should turn it clockwise. 4. All dials, like altimeter setting and lighting should be able to click and drag in VR with mouse disabled 5. All dials as in point 4 should also work using mouse scroll wheel 6. Include keybinds for all switches, please include a bind for each state, and a bind for toggling a state. E.g. there is no keybind to show/hide the pilot body. Please also make gear and hook as toggle buttons as well. I think something like the master arm only has one possible state at the moment. Many hardware users need ON/ELSE or OFF/ELSE type key binds as well. (Look at the Hornet for example, the "special" cases). Thanks in advance! Fresh

Check out this post to make a keybind for the pilot body:

@_Hoss Try clicking on the payload restriction box, see if that helps to show the possible ordinance.

I tried flying at night, noticed that the "M" label that is stamped on the mixture control, does not match position with the lever, but floats a bit aft of it. (Misaligned texture I guess.)

You can load them on an air start mission. I selected the option to see the station limitations, and then selected them like that, but it didn't work in the usual manner.. but maybe I did something wrong...

I fixed the Tiny Tim rockets mission, see attached .miz file. Fresh F4U - 08 - Tiny Tim rockets.miz

They forgot to add them.. I edited the mission and included them. See attached. Cheers, Fresh F4U - 08 - Tiny Tim rockets.miz

Hi Ginsu, can you post a track? Did you try another date with GPS to troubleshoot? Is there wind? Thx, Fresh

Hi, please post a track so we can help you. Thx Fresh

Hi, I've experienced a couple of occasions where the required ground speed puts me at TOT over the waypoint before my target, i.e. at my IP. I have not been able to find what causes this. I created a mission to test this. It has 6 waypoints, each 6nm apart from each other (total 36nm). If you delete waypoint 3 the total distance is then exactly 30 nm. Flying at 360 knots GS means it takes either 6 minutes or 5 minutes (depending if you delete waypoint 3 or not). If I delete waypoint 5 the total distance and time is the same, since it is a straight line between waypoint 4 and 6. In the replay you can see the HSI wants me to come to a standstill at waypoint 4. Something is breaking the calculation. I have SEQ1 boxed, AUTO is boxed and the next waypoint ahead is selected. This sometimes works and sometimes it doesn't. Deleting a waypoint in the sequence (before entering any TOT data) might be one of the causes, I can't show it conclusively. Fresh TOT with GSPD bug.trk TOT Test Caucasus.miz

The possibility to load a DTC to all aircraft in a group is nice, but with complex squadron missions, with perhaps 10-20 groups of the same type it would help mission makers and updaters' life much easier if you could assign a default (and preloaded) DTC to all aircraft of a specific type in a coalition. The current "load to group" option is cumbersome, as each group has to be selected, and the first in the group clicked to see the rest. Even now, the DTC is inserted in the jet to be activated later. It would be better if it would be directly active on mission start. (At the moment this is only possible via the attributes tab, and has to be done for each jet.)

If I create a new group and set this attribute (i.e. check the check box), when I increase the number of aircraft in the flight, the new aircraft don't have this attribute on creation, and I have to check each aircraft individually.

Definately this is required!

Sorry, now I think I understand your question. The MUMI page just shows what was loaded at mission start (which is controlled by the mission editor.) I agree, it would be good to see the file name of the imported DTC file. Since you can change the values after importing, it would not necessarily be what was in the file, so maybe an asterisk after the file name could indicate a modified DTC setting (vs the original file). ?

I made some comments ^ there ^

...and when entering a frequency (in the DTC manager window) it changes from AM to FM without user input.

I noticed two things: The DTC COMMS Menu is bugged and doesn't save or display the modulation correctly. If I save as AM it is FM in the game. I manually edited the .dtc file, replacing "modulation": 1, with "modulation": 0, and it is then correct when loaded from the DTC. The second thing: if I want to change from AM to FM and vice versa, I have to press the FM/AM button, then press ENT on the UFC, then change back and forth to see the change.

I edited the .dtc file to set all threat to AUTO = None.. now in a test mission it will still dispense flares when an SA-2 locks me. Unfortunately I can't send a track file, they are bugged (reported) Auto4.trk ALE-47 DTC Test.miz Test AUTO is NONE.dtc

you have to assign the DTC in the mission editor for the aircraft (last tab in the properties) and check "load default" on mission start.. (or words to that effect).

I have the same problem... using 2D I tried with and without opening the DTC menu from the briefing/fly screen. Auto4.trk

That is a screenshot of page 408 in the DCS F/A-18C Early Access Guide dated 24 March 2024, in case someone is looking for the source.