Thank you very much. You have totally hit the mark with your suggestion. Problem solved, it seems. It was the language, Install the English(UK) language pack and log in with English as the language. The language I use is Spanish (Spain). Can't play with my language?
Release Elite Cougar MFD Cockpit Display - game changing new companion app
- Thread starter Bionic Bytes
- Start date
I have tried to support different languages. I’ll investigate and check why Spanish isn’t working.
Thank you very much. Is there a reason why I can't drag the windows? I've paused them, as indicated, but they can't be dragged. There is no way to move them.
Interesting, you should be able to. When paused, the windows should have the familiar window title area which allows the window to be repositioned. When running (not paused) the title area is removed and then the windows are fixed. Additionally, when paused the windows appear a solid background colour.
Do you have a screen shot of what's happening?
The window positions are saved in a file called "MFD.ini" and there are entries for the x,y width and height, eg
[MFD1]
WindowX=1921
WindowY=550
WindowW=528
WindowH=488
As a work around, you can manually adjust these values before running the EXE if you know where you want them positioned.
Did you try the MFDWindowTest that I pointed to in the previous post? This utility uses the same rendering/window code and helps me work out if there's a problem with window/OpenGL handling on your system. Please let me know if this utility has the same window pause/drag issue.
Last edited:
I already managed to drag laws windows. I did it before entering the game and without problems. Thank you. Now what happens is that the keys on the MFD Cougar do not match the symbols seen in the images. For example: The pilot assistant symbol does not match the corresponding button on the cougar. I guess I have to configure it manually right?
The user manual explains this process in some detail.
In simple terms - you must set the key press to match Elite or set elite to match the key binding for this app. There is a quick key assign which will map those icon key binds and force elite to use the same, or you can make this app use the key press which elite is using.
it’s all held on the XML files in the application folder if your interested in the finer details.
Okay, I take note. Thank you very much for all the help you have given me. You've been very kind. : )
Version 1.20.0.0 Released
New utility shipping with this application - EliteKeyTester
This tool uses the same underlying code as the main application and is therefore a light weight testing tool which can be used to check why a certain key combination is not working with Elite Dangerous.
-----------------------------
Changes in this version:
FleetCarrier – various fixes including:
- Corrected location updates
- Odyssey updates to finances (rearm,refuel,repair,pioneer tax rates)
Orrery
- Odyssey planet filter
Weapons console
- Target pilot name and rank
Application launching
- MFD Cougar – display window titles on first start
- Single thread – debug option
Key Press
- Added delay between switching to Elite Window and sending keys
- results in better Elite key press processing
Custom key presses to the MFDLayout Editor
- Can override the MFD_Iconset.xml default key assignments
New utility shipping with this application - EliteKeyTester
This tool uses the same underlying code as the main application and is therefore a light weight testing tool which can be used to check why a certain key combination is not working with Elite Dangerous.
-----------------------------
Changes in this version:
FleetCarrier – various fixes including:
- Corrected location updates
- Odyssey updates to finances (rearm,refuel,repair,pioneer tax rates)
Orrery
- Odyssey planet filter
Weapons console
- Target pilot name and rank
Application launching
- MFD Cougar – display window titles on first start
- Single thread – debug option
Key Press
- Added delay between switching to Elite Window and sending keys
- results in better Elite key press processing
Custom key presses to the MFDLayout Editor
- Can override the MFD_Iconset.xml default key assignments
Version 1.21.0.0 Released
Update to support Odyssey update #12
-----------------------------
Changes in this version:
Fixed Nav Route cutom panel. Now always highlights current system
Added FSSBodySignal event
Fixed json decode in SAASignalsScan event
Countdown timer panel
- better display of time (in mins/sec)
- FleetCarrier jump specific messages
Update to support Odyssey update #12
-----------------------------
Changes in this version:
Fixed Nav Route cutom panel. Now always highlights current system
Added FSSBodySignal event
Fixed json decode in SAASignalsScan event
Countdown timer panel
- better display of time (in mins/sec)
- FleetCarrier jump specific messages
Version 1.22.0.0 Released
Changes in this version:
Support for Odyssey update #13
- Added new journal event NavRouteClear
- Added DestinationSettlement as a new optional parameter for the MissionAccepted event
- Added Genuses parameters in SAASignalsFound event
Changes in this version:
Support for Odyssey update #13
- Added new journal event NavRouteClear
- Added DestinationSettlement as a new optional parameter for the MissionAccepted event
- Added Genuses parameters in SAASignalsFound event
Version 1.23.0.0 Released
This version focuses on mining (specifically laser mining) with some significant improvements for EDDB integration.
Changes in this version:
Fix to Callouts.json - Lakon spelling mistakes corrected
Journal Events - improved journal reading (prevent skipped events)
Added support for the following events: FuelReservoir
Better cargo limpet tracking following changes to Odyssey updates
Commander's Log
- Added ability to search EDSM for pristine metallic ringed systems (useful mining tool)
- Codex entry query
Explorer Log
- Fixed issue with importing commodities
- Optimised commodity searching (downloading/import/search)
This version focuses on mining (specifically laser mining) with some significant improvements for EDDB integration.
Changes in this version:
Fix to Callouts.json - Lakon spelling mistakes corrected
Journal Events - improved journal reading (prevent skipped events)
Added support for the following events: FuelReservoir
Better cargo limpet tracking following changes to Odyssey updates
Commander's Log
- Added ability to search EDSM for pristine metallic ringed systems (useful mining tool)
- Codex entry query
Explorer Log
- Fixed issue with importing commodities
- Optimised commodity searching (downloading/import/search)
Version 1.24.0.0 Released
Focus of this release is the Layout Editor and Custom Icons Editor.
Next release in January will support changes that Odyssey #14 update has made.
-----------------------------
Changes in this 1.24.0.0:
Improvement to minimize application to system tray with multiple active OpenGL context windows (MFD consoles such as Flight,Weapons, Custom consoles).
- Some windows would not restore properly. Increased delay between activating the window and switching OpenGL context.
Fixes to Custom Icon Editor
- Correctly allows multiple textures in the texture sets and adds <icons> xml nodes
- Adds ability to switch between icon sets and ability to delete icon sets
Fixes to Layout Editor:
- Radio Chatter: fixed icon assignment bug.
Previously when saving/closing the UI, the icon ID value associated to the RadioChatter was erronously assigned as -1 instead of its default value (60); this resulted in the icon disappearing from supercruise. A new MFD_Layout.xml has been shipped with the full version .zip package.
- Hotkey assignments to buttons
Previously, keys assigned to the MFD icons in the layout editor had to be associated with an Elite action because these key sequences were being send to Elite to perform some function (the Elite Binding, such as toggle ship lights). Whilst this is generally desirable, there are some very specific cases where we want to display a custom icon in the MFD grid but not send a key sequence to Elite; instead we want the icon to flash/animate and for some other action to occur. An example of this is the "Radio Chatter" icon feature - which tracks the status of the Air Traffic Control "ATC Simulation" on/off toggle. By setting the hotkey flag in the button UI, the keypress can be assigned to a "customAction" to perform the toggle.
Note: Unlike regular Elite key press sequences (which could be a key press with several modifier keys such as LeftShift or RightControl), hot keys have no distinction between left/right modifiers.
Note: F12 (without a modifier such as SHIFT) can't be used as a hotkey - see https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-registerhotkey
- Play sound when MFD button pressed
Thrustmaster MFD Cougar button presses often feel soft (non-tactile). Playing a sound can prevent additional suprious button presses as the user is assured that the MFD button press has been registered.
- Latch button presses
Prevent too many spam MFD button presses within a time period (in milliseconds). Default is 1000 ms.
There is one global button latch time value per layout (flight,weapons,SLF,supercruise, etc).
Focus of this release is the Layout Editor and Custom Icons Editor.
Next release in January will support changes that Odyssey #14 update has made.
-----------------------------
Changes in this 1.24.0.0:
Improvement to minimize application to system tray with multiple active OpenGL context windows (MFD consoles such as Flight,Weapons, Custom consoles).
- Some windows would not restore properly. Increased delay between activating the window and switching OpenGL context.
Fixes to Custom Icon Editor
- Correctly allows multiple textures in the texture sets and adds <icons> xml nodes
- Adds ability to switch between icon sets and ability to delete icon sets
Fixes to Layout Editor:
- Radio Chatter: fixed icon assignment bug.
Previously when saving/closing the UI, the icon ID value associated to the RadioChatter was erronously assigned as -1 instead of its default value (60); this resulted in the icon disappearing from supercruise. A new MFD_Layout.xml has been shipped with the full version .zip package.
- Hotkey assignments to buttons
Previously, keys assigned to the MFD icons in the layout editor had to be associated with an Elite action because these key sequences were being send to Elite to perform some function (the Elite Binding, such as toggle ship lights). Whilst this is generally desirable, there are some very specific cases where we want to display a custom icon in the MFD grid but not send a key sequence to Elite; instead we want the icon to flash/animate and for some other action to occur. An example of this is the "Radio Chatter" icon feature - which tracks the status of the Air Traffic Control "ATC Simulation" on/off toggle. By setting the hotkey flag in the button UI, the keypress can be assigned to a "customAction" to perform the toggle.
Note: Unlike regular Elite key press sequences (which could be a key press with several modifier keys such as LeftShift or RightControl), hot keys have no distinction between left/right modifiers.
Note: F12 (without a modifier such as SHIFT) can't be used as a hotkey - see https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-registerhotkey
- Play sound when MFD button pressed
Thrustmaster MFD Cougar button presses often feel soft (non-tactile). Playing a sound can prevent additional suprious button presses as the user is assured that the MFD button press has been registered.
- Latch button presses
Prevent too many spam MFD button presses within a time period (in milliseconds). Default is 1000 ms.
There is one global button latch time value per layout (flight,weapons,SLF,supercruise, etc).
Hi All. I currently have 2 x Cougar MFD fitted onto a 11.6 screen (used for the MFDs in DCS). Can I display both displays onto this single screen. Secondly - I have an additional 11.6 screen with another 2 Cougars bolted to it (cannot have enough system displays in DCS!!) . Is it possible to run 4 cockpit displays at the same time?
Thanks in advance.
Thanks in advance.
Yes no problem. You can arrange upto 8 additional displays and arrange them on to any number of additional monitors. In your case you’ll simply arrange the two default mfd cougar displays and arrange them side by side on your 11.6 monitor. Your first two thrustmaster cougar joysticks are automatically assigned to these two windows.
You can then easily assign another two “custom” info displays to your other monitor and also assign any joysticks - including extra thrustmaster mfd cougars - as inputs.
There is a comprehensive manual but I think the GUI is fairly intuitive.
Good luck!
Many thanks for the quick reply - really looking forward to giving it a go and having a play - the various videos look awesome - so well done to you and the effort you have put into it. Next question - what is the difference/drawback between the licensed/donation version and the plain download?
There is no difference. Just a nag timer message from time to time
OK - so fired it up, it ran through its various downloads, and...??*@!!? Thoroughly confused!
Hit pause, resized/placed the windows onto my 11.6 within the 2 cougar display areas, selected resume and they stayed grey. Went back to the widget, hit start and they resized to the original smaller sizes they were when I dragged them into the screen. Only the right screen appeared to be displaying. Did a restart - got a CPU temperature warning. Disregarded the warning and went back at it. Bit more success this time, both screens were displaying something, hit pause, to try to resize - only one grey screen displaying across 3/4 of the overall large screen? Did a couple more reboots with corresponding temp warnings and managed to get both screens sort of showing but seems to be a bit hit or miss.
I am running it from a secondary drive - does it need to be unzipped and run from the C drive?
Basic issues/questions:
Resizing the windows doesn't always 'take'.
The start/pause/resume doesn't always appear to work (managed to resize windows without pausing?). Hit pause, make some resizing changes, go back to the widget and still have the option to pause?
Everytime I reboot after running the program I get a CPU temp warning?
Do I need to do something to get the cougar keys to work?
Sure there'll be more questions until I get it running properly (as I want it to run properly - looks awesome!) but ran out of time today!
Hit pause, resized/placed the windows onto my 11.6 within the 2 cougar display areas, selected resume and they stayed grey. Went back to the widget, hit start and they resized to the original smaller sizes they were when I dragged them into the screen. Only the right screen appeared to be displaying. Did a restart - got a CPU temperature warning. Disregarded the warning and went back at it. Bit more success this time, both screens were displaying something, hit pause, to try to resize - only one grey screen displaying across 3/4 of the overall large screen? Did a couple more reboots with corresponding temp warnings and managed to get both screens sort of showing but seems to be a bit hit or miss.
I am running it from a secondary drive - does it need to be unzipped and run from the C drive?
Basic issues/questions:
Resizing the windows doesn't always 'take'.
The start/pause/resume doesn't always appear to work (managed to resize windows without pausing?). Hit pause, make some resizing changes, go back to the widget and still have the option to pause?
Everytime I reboot after running the program I get a CPU temp warning?
Do I need to do something to get the cougar keys to work?
Sure there'll be more questions until I get it running properly (as I want it to run properly - looks awesome!) but ran out of time today!
A few things.
Are you using a AMD GPU?
Their latest drivers have broken OpenGL compatibility so you’ll need a driver set from some time ago. Have a look on my discord channel for that conversation recently.
There is some debugging in the Logs folder which you can Send me and that will help me diagnose possible problems.
The app needs to be unzipped into a folder on any drive.
The issues you are having seem like AMD driver issues and some sort of GPU crash.
There are some debug tools on the website downloads to help diagnose possible GPU driver issues.
Are you using a AMD GPU?
Their latest drivers have broken OpenGL compatibility so you’ll need a driver set from some time ago. Have a look on my discord channel for that conversation recently.
There is some debugging in the Logs folder which you can Send me and that will help me diagnose possible problems.
The app needs to be unzipped into a folder on any drive.
The issues you are having seem like AMD driver issues and some sort of GPU crash.
There are some debug tools on the website downloads to help diagnose possible GPU driver issues.
The cougar keys will work once you have read the manual on this topic. Basically you need to map the icons to elite actions. This is all handled via xml files which is done for you by the Layout Editor. First things first though you need to stop the crashing which I believe to be a driver issue from the sound of it. I know that there is no issue with NVidia or intel dtivers and my legacy AMD R9 385 is working fine. It’s AMD newer generation of hardware and their new driver suite which seems to have completely broken basic Open GL rendering. There’s even a thread on Elites forum for a known issue with the same driver suite and the DX11 rendering.
Last edited:
AMD CPU with Nvidia 3090 GPU. No AMD GPU drivers anywhere near my system...
Just booted it all up again, so started CD, launched elite, got through to being sat in my cockpit, went to the widget and selected start - grey screen - just 1 - across 3/4 of my 11.6, with which I can do nothing. Tomorrow will try setting them up on a standard display instead of the smaller cougar mounted display to see if there is any difference made.
I am getting a lot of Norton warnings though when i try to run it - which I think I am authorising access...
Just booted it all up again, so started CD, launched elite, got through to being sat in my cockpit, went to the widget and selected start - grey screen - just 1 - across 3/4 of my 11.6, with which I can do nothing. Tomorrow will try setting them up on a standard display instead of the smaller cougar mounted display to see if there is any difference made.
I am getting a lot of Norton warnings though when i try to run it - which I think I am authorising access...