mkiii

With a multi monitor setup, using windowed mode, I have Monitor1, Main Monitor, Monitor2 etc. So the default position for the Controls indicator is off to the bottom left. This is neck strain country. I normally, edit the ControlsIndicator_page.lua to set the new base position. For some inexplicable reason, the Mig21 has that file as a compiled binary file named cip This is done on other files, but this is the one I want to get at. Why on earth do this? - There shouldn't be any secret code in there!

The FC aircraft? They have no control indicators. The files just aren't there. Maybe in another 15 years ED will actually make a proper multi monitor support that works without having to mod the crap out of it. I'm not holding my breath though. The impetus is to keep producing new stuff rather than fixing the old issues.

For the current discount cost of $14.99; (Which I assume is only for current FC owners), it seems a reasonable price, even if it is just for one extra aircraft. It is for me, since I don't have the Mig-15 or F-5.

Yes. Same problem here. During the training exercise, I got it to work perfectly, when I made sure I was trimmed up, on the correct heading (aligned with the runway), within a few degrees of the WP1 heading, and at the correct altitude and speed way before approaching WP 1. One proviso - I set my sped a bit slower than recommended, at just 160kmh - which seemed to help. I did not touch route mode until I had set DH/DT to auto, and DH sub mode on the AP panel. I also did not touch the INS Gyro switch - which starts off in the mid position. I suspect that lowering my speed and maintaining a roughly correct heading initially is what made it work for me, if you are off track, you end up with a large turn radius that causes you to miss all the waypoints.

I would be happy if either one of them got a clickable cockpit at the very least, but I'm not holding my breath.

It has never worked for me in any multi monitor setup. You should be able to see it if you press ALT+ENTER, but you run the risk of messing something up when you do that, and you will have to do it every time you want to use the thing. This is unacceptable IMO. There NEEDS to be an option to manually place it, and ALL those floating windows that DCS uses such as Kneepad, Control Indicator, AI controls for AH64 etc.

And here we are in 2022. Nothing has changed. Still no way of editing the position of the thing.

I guess the lesson for some, is to actually read the thread before wildly flailing about and reinstalling everything. Always remove mods before updates. All the hacks we see on these forums WILL break something eventually if you don't manage them properly.

It's a shame, I was enjoying the mod.

The fix shown above is already IN the latest update - it even has a link to ASTO... Either way, the result for me (3 main monitors sideways, +1 extra for mfds to the far right)) is identical to the first release, ie the CPG menu is on screen 1 halfway off the bottom, with the Pilots menu nowhere to be seen. YES I know how to bind them. IMO, this and the control indicator NEED to be movable like the Kneepad, although even that insists on disappearing off to the furthest right monitor and still needs a slight mod like this one to make it appear on the 1st monitor by default. This is not 1990, things like this should not be hard-coded. My fix using the ORIGINAL file places them on the leftmost menu, near the middle. YMMV GREEN STUFF IS MY EDIT Adjust compas_pos & weap_control_pos --not for VR! compass_pos = {-0.8 * total_aspect, 0.5} -- ORIGINAL LINE {-0.82 * total_aspect, -0.7} --relative to screen center, 1 equals screen height afaik weap_control_pos = {-0.8 * total_aspect, 0.5} -- ORIGINAL LINE {0.8 * total_aspect, -0.75} --viewports stuff local v = find_viewport("GU_MAIN_VIEWPORT", "CENTER") if v ~= nil then if v.width ~= total_w or v.height ~= total_h then ULX = v.x ULY = v.y SZX = v.width SZY = v.height local aspect = SZX/SZY -- NOTE ALL THE STUFF IN BLUE IS DIFFERENT IN THE LATEST UPDATE weap_control_pos = {(ULX + SZX / 2 - total_w / 2) / total_w * total_aspect * 2, -(ULY + SZY / 2 - total_h / 2) / total_h * 2} compass_pos = {weap_control_pos[1] + compass_pos[1] * SZX / total_w, weap_control_pos[2] + compass_pos[2] * SZY / total_h} weap_control_size = weap_control_size * v.height / total_h compass_size = compass_size * v.height / total_h end end --end viewports stuff end

Messing with lua files like this (as we currently have to do to position the control indicator for example) is not a "solution". It is a hack that could be broken by next week. Don't worry guys. It only took a few years to make the Kneepad movable, and in a few more, we may even get an option to select a start position in the main menu, for in-game UI, so you never know. That may also apply to the Control indicator & the AI menus.

A lua file in the MB-339PAN folder, in your User mods folder causes the crash. Not in your app install folders. Mods should always be removed, from both Users/userName/Saved Games/DCS/Mods (or DCS.Openbeta/Mods, depending on your setup), and your DCS install folders before installing updates.

The MB339 is officially broken now. Take a look at their page. The last but one page does have a fix to allow it to be used, but the module still does not function correctly with this version of DCS. Note: You must remove the MBB339PAN folder completely from your Users\Username\Saved Games\DCS.openbeta\Mods\aircraft. If that dosn't work, then you probably have another mod with a problem. Remove them all to start with. Reinsert one at a time. to find out which.

Just Downloading now... And I see that already people are complaining about it! What do you want guys? Read the T&C and meaning of "Early Access" before you start. Meanwhile congratulations to the team, getting it out under such trying circumstances. PS: little congrats to me too. This is post 666 - that has to be significant in some way

Grey, green and black. Exciting times!