Loophole

For me the binding was RCTRL+RSHIFT+K, not RAlt.

I was having problems with GBU-24 loadouts on my F/A-18, and tracked the issue down to a misunderstanding of what the "Copy to all of same type of weapon" button does on the Fuse Settings panel in the Loadout screen. Note: You only get this button when changing fuse settings for a laser-guided bomb. My assumption was that the button applied ALL of the weapon settings on that panel to all of the other weapons of that type. Turns out it does not - it only applied the laser code, not - for example - the fuse choice. As a result I ended up with multiple fuse types, which the F/A-18 stores system doesn't like (displays ADV-LOAD on the MFD, and bombs won't drop). I can suggest two possible changes that could improve this: Change the button text to be a bit more explicit; E.g. "Same code for all this weapon type". Change the button function to apply all settings (which would then make it a useful button to have on all the fusing panels)

I agree, its a very nice tool. I think a neat enhancement down the track would be dynamic sharing of routes. I'm imagining somebody playing in - say - a ground commander slot being able to sketch out a flightplan, save it as e.g. "ALPHA-01", then be able to tell a pair of players "load flightplan ALPHA-01". I imagine that to achieve this there would need to be some sort of special pool of flight plans that are saved on the server rather than privately on each client. They'd need to be coalition-specific too.

Please please please tell me more about Dynamic Slots! How will they work? What will they do? What colour will they be? Mission developers the world over need answers, to bring them hope!

Power Lever jittering for the CPG still occurs in the current version: 2.9.5.55918

Same for me. update_screenspace_diplacement is the right name for the method - if you do a search of all the Lua scripts in DCS you'll find its defined in ViewportHandling.lua with that misspelled name. I found that putting in the call with corrected spelling resulted in no export at all for me - I'm assuming the scripts fail because they can't find the method. I didn't test your full process, though; I only tested putting the call into the "initxxx" lua's. Oddly, early on in my testing the "TV on the HUD" thing happened to me, but in all my subsequent tests it hasn't happened again; just the full-screen grid, even with TV up on the DSCG. One thing I did notice is that the grid itself (but not the horizon line) is a texture, not drawn lines - which in itself makes no difference, but does explain how it come to exist when the draw_grid and draw_ppi_grid methods in radar_page.lua never get called by anyone. I've put a post about this in the Bugs sub-forum, so hopefully Heatblur will notice and put it on their to-do list, if it isn't there already.

I think the method name you meant to use is update_screenspace_diplacement - with the typo in the name?

I've *almost* been able to get the DSCG export working. I can get the radar and the Maverick TV display to export to a viewport, but when I do that I *also* get the radar grid-lines (only) displayed full-screen across my entire view! Have not found why that is or how to stop it happening, which is frustrating because otherwise the export works really nicely! What I did was add the lines: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F4E_DSCG", "RIGHT_MFCD") at the end of the two files: F-4E\Cockpit\Scripts\DSCG\indicator\init.lua F-4E\Cockpit\Scripts\DSCG\Indicator\DSCG_Pilot\init_bake.lua ("F4E_DSCG" being my custom viewport defined in monitorconfig, of course) It would be really nice if this could be enabled!

I've *almost* been able to get the DSCG export working. I can get the radar and the Maverick TV display to export to a viewport, but when I do that I *also* get the radar grid-lines (only) displayed full-screen across my entire view! Have not found why that is or how to stop it happening, which is annoying because otherwise the export works really nicely! What I did was add the lines: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F4E_DSCG", "RIGHT_MFCD") at the end of the two files: F-4E\Cockpit\Scripts\DSCG\indicator\ init.lua F-4E\Cockpit\Scripts\DSCG\Indicator\DSCG_Pilot\init_bake.lua ("F4E_DSCG" being my custom viewport defined in monitorconfig, of course)

The "Toggle Body" binding works fine, but the "Hide" binding shows, and the "Show" binding hides.

Ok, had to go and watch a darned YouTube video to discover the secret - Press & hold the Jester UI button for a long press. Was that mentioned in the manual somewhere?

I cannot figure out how to get rid of the radial menu. I've tried all the keybinds I can think of, but nothing seems to work. Please; what am I missing?

Just as an FYI to anyone (like me) coming upon this topic at a later date - I was struggling with the same problem, but it wasn't the "auto handover" setting that was causing the issue; I was using the Instant Action "Runway Start" mission as a place to get my keybinds in order; that has "simplified AI" set in the mission parameters, and that also seems to prevent use of the CPG sight.

I have to say I was also a little confused as to what I now had installed, as the folder is still named DCS Open Beta. After reading through some of the other threads I gather that it doesn't matter whether you are Open Beta or Stable; both update to the same version, and in the future they will do something about standardising the folder name. (but right now we can just carry on with whatever "branch" we were on, as they are both the same.

Bug is still present in Feb 2024 - encountered while trying to STORE a target selected using the TADS from about 4km away. The stored position was consistently several hundred meters west of the targeted spot (ownship heading roughly 180 at the time). This is in the latest Open Beta build at the time.