Release Elite Cougar MFD Cockpit Display - game changing new companion app

[Bionic Bytes]

I've been trying to get this to run. The displays come up and do their thing. My issue seems to be with the keybinds. In the main window the "Elite Keybindings Folder" is correct. But when I try to do "Edit Layout" a window comes up saying "Elite is not configured to use Custom bindings. Currently using:Custom*". Pushing past this the "Select your Elite Dangerous key binds file" is dark gray and won't allow me to enter the file name on the line. I've tried rebooting and starting up in the correct order, but am still stuck. I can configure Elite Dangerous directly and tell it to use MFD Cougar buttons, but I think that's not the intent here? I could use a push in the correct direction.
View attachment 351327

Typically, Elite's keybinds are in a folder C:\Users\xxxx\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings
This folder path needs to be entered into the main application page, along with the path to Elite's journal: C:\Users\xxxx\Saved Games\Frontier Developments\Elite Dangerous
These values are then saved into the registry: Computer\HKEY_CURRENT_USER\Software\BionicBytes\EDCD

In the bindings folder, there should be StartPreset.start file which has the content Custom
Then you'll find the file Custom.4.0.binds which is an xml file containing key assignment mapping.
However, you won't get these files until you customise the key bindings in Elite and make a change to a mapping.

Let me know how you get on.

 

[Cmdr Alzaroc]

Typically, Elite's keybinds are in a folder C:\Users\xxxx\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings
This folder path needs to be entered into the main application page, along with the path to Elite's journal: C:\Users\xxxx\Saved Games\Frontier Developments\Elite Dangerous
These values are then saved into the registry: Computer\HKEY_CURRENT_USER\Software\BionicBytes\EDCD

Yes, verified that yesterday, except for the registry.

In the bindings folder, there should be StartPreset.start file which has the content Custom
Then you'll find the file Custom.4.0.binds which is an xml file containing key assignment mapping.
However, you won't get these files until you customise the key bindings in Elite and make a change to a mapping.

OK, here's my finding. My folder has two StartPreset files in it. The one in use has a .4 after it as does my custom binding file. The StartPreset WITHOUT the ".4" is very old and doesn't have a custom listed. Elite is not using this one, but the .4 one, however I changed the old StartPreset to the same as the .4 one and now Cougar Display can find the bindings.

However, Elite Key Assignments and Available are both blank. I think it doesn't like that I changed the name of my Custom Binds to a different name. I did that to make sure Elite didn't rewrite my binds on me with the default one. I'm not sure though why, since it definitely found the right keybind to list in the app.

 

[Bionic Bytes]

Yes, verified that yesterday, except for the registry.



OK, here's my finding. My folder has two StartPreset files in it. The one in use has a .4 after it as does my custom binding file. The StartPreset WITHOUT the ".4" is very old and doesn't have a custom listed. Elite is not using this one, but the .4 one, however I changed the old StartPreset to the same as the .4 one and now Cougar Display can find the bindings.

However, Elite Key Assignments and Available are both blank. I think it doesn't like that I changed the name of my Custom Binds to a different name. I did that to make sure Elite didn't rewrite my binds on me with the default one. I'm not sure though why, since it definitely found the right keybind to list in the app.

I noticed this on my machine as well, but because StartPreset.start exists with "Custom" as the only entry, I've been ignoring it. I may make a change for the next version to check for StartPreset.4.start file.
Having looked at mine, it contained an entry "KeyboardAndMouseOnly" and crucially this was the last entry. This is what's causing your issue - because I was expecting the file to contain just a single entry "Custom" - or at the very least, the last entry. Next version will just look for "Custom" no matter where it is.
My observations are that when StartPreset.start contains "Custom" then there is a "Custom.4.0.binds" file to load which is the key mapping xml for Elite.

 

[Bionic Bytes]

Version 1.28.0.0 Released

With the closure of EDDB.io the application will migrate away from EDDB and replace the functionality lost with something equivalent or new, starting with release 1.29.0.0


Changes in this version:

Fixes:
LayoutEditor:
- KeyBindings - detects for the presence of StartPreset.4.start file as well as StartPreset.start
Main application:
- Commander's log tab - "Show" button now restores previously minimised commander's log window
- Air Traffic Control tab - joystick axis selection
volume level corrected for axis values between -1.0 and 1.0.
UI improved so that joysticks with the same GUID are further differentiated by name. This fixes issue that selected joystick is not found/used for volume control.

Mission Explorer:
- EDDB - no longer runs the schedule to download EDDB databases. For now, the functionality still exists to manually download (assuming the site is still running).
- "Commodity Search" tab renamed as "Commodity Search EDDB" to show its reliance on EDDB.io providing data

 

[Bionic Bytes]

Version 1.29.0.0 Released
EDDB.IO site has closed and therefore changes are necessary to Cougar Display.

To mitigate some of the functional loss I have released version 1.29.0.0 today, ahead of the May release schedule.
This releases completely removes EDDB and starts the integration with INARA - with more to come over the next few releases.

New Features:
Mission Explorer:
- EDDB - download and import last available systems_populated.json from EDDB (used as a quick filter on system name by the UI)
- INARA commodity search integration
- "Commodity Search" tab renamed as "Commodity Search INARA" to show its reliance on INARA.cz providing data
- Debugging option added to MFDCougar.ini - [INARA] DebugQuery=1 to log API calls to LOGS folder
Changes
- removed legacy code due to EDDB integration
- improved application start-up times (EDDB database/import no longer required)
- reduced memory footprint due to EDDB tables

 

[Bionic Bytes]

Version 1.30.0.0 released

This version focuses on Route Optimisation (bulk passenger/Source/Delivery missions) with a new algorithm for better results.

• now considers cargo capacity and jump range
• cache INARA commodity search results for speedy results (source/supply missions)

 

[Bionic Bytes]

Version 1.31.0.0 is released

EDDI.io site is closed, all functionality replaced by INARA

EDDB integration has been removed; Commodity/System state searching the local EDDB database has been removed.
Market data (custom panel) will no longer work when trying to extract a system's imports/exports.

functionality Lost due to EDDB closure:
1. custom panel - system imports/exports on FSD jump

functionality replaced with INARA:
1. Mission Explorer - commodity searching
2. Route optimisation builder - commodity searching
3. EDDB database import - station/state searching UI
4. Auto-complete text prompt when typing in system names (Mission Explorer: commodities search; Waypoint system names)

-----------------------------
Changes in this version:

INARA integration - Search near "me" for:
Material trader
Tech brokers
Interstellar Factors
Fleet Carrier Outfitting
Scorpion SRV vendors
Anarchy Systems in Outbreak
Damaged Stations
Compromised NAV Beacons
Various BGS State (eg systems in Boom + War, etc)

 

[Bionic Bytes]

Version 1.32.0.0 Released

Changes in this version:

Odyssey update #15 support
Journal changes - SupercruiseDestinationDrop event added, some others added extra information
Additional events added to the cusomisable file "SpeechEvents.json" / Speech Editor which adds "ThargoidInterdicted" and "SupercruiseDestinationDrop" (threat alerts)

New Features:
Can now select any OpenGL texture and display on a custom panel.
New Elite icons added and available as textures
- Logos of Takada, Supratech, Remlock, Manticore, Kinematic Armaments
- Ship modules and weapons, including the following:
AFMS, Cargo, limpet, Experimental Weapon Stabiliser, FSD Booster, FSD Interdictor,Fighter Hanger,Flight Assist
Hull Reinforcement, Passenger Cabin, Vehicle Hanger, Shield Generator, Shield Cell Bank, Scanner, Refinery
Power Plant, Thrusters, Life Support, Power Distributor, Heat Sink, Point Defence, Chaff, Multicannon, Beam Laser, Missile Rack, Mining Laser

 

[ilmostro]

Mmmm - I'm soooo going to have to give this a try, cause....

Source: https://youtu.be/kjTEYlP760A


iPad mini retina display (you canbuy them as replacement parts) and an adapter to run it off USB power and Displayport input. Nice size for the MFD, native resolution of 2048×1536 (326 ppi), so probably 1450x1450 usable?

 

[ilmostro]

Fortunately, I remembered where the display was:

From actually measuring the size of the MFD, I think something about 1385x1385 would be usable.

 

[Bionic Bytes]

Fortunately, I remembered where the display was:

View attachment 364793


From actually measuring the size of the MFD, I think something about 1385x1385 would be usable.

wow, cool idea.
Touch pad/screens are supported, so this setup looks ideal.

 

[ilmostro]

wow, cool idea.
Touch pad/screens are supported, so this setup looks ideal.

Unfortunately, although the "digitizer" - i.e the the bit that detects touch is usually supplied in the spare part, AFAIK none of the adapters can actually use it. Although I bought mine over 5 years ago, so things might have changed.

The real benefit is that the screens are really high quality, and weren't that expensive.

Just checked my receipts:

Screen £58 GBP off EBay

Adapter £28 (was priced in Japanese YEN - 3920 JPY)

So £86 including shipping. Only extra costs would be a Display port to Mini DP, and a USB cable, and whatever you need to mount it / make a case / ETC.

 

[Bionic Bytes]

Unfortunately, although the "digitizer" - i.e the the bit that detects touch is usually supplied in the spare part, AFAIK none of the adapters can actually use it. Although I bought mine over 5 years ago, so things might have changed.

The real benefit is that the screens are really high quality, and weren't that expensive.

Just checked my receipts:

Screen £58 GBP off EBay

Adapter £28 (was priced in Japanese YEN - 3920 JPY)

So £86 including shipping. Only extra costs would be a Display port to Mini DP, and a USB cable, and whatever you need to mount it / make a case / ETC.

£86 for a high quantity , hi res screen. Bargain.

 

[Bionic Bytes]

Version 2.32.0.0 is released

Changes in this version:

• First version of the new 2.x series of MFD Cougar Display.
• OpenGL profile switched to 'core' from 'compatibility'
• Fixes issues with latest AMD hardware/drivers

 

[JetMac4Life]

Hi BB.
I just got the CD latest release and installed per your user's manual. Almost everything is going as described. The issue I am having is when I make ED go full screen, it moves one display to the right and one display disappears. I have 3 monitors total, main is a 75" TV, the other two are 7" touch screens in my sim pit, upper L & R, I am running an AMD Ryzen 7 3800X 8-Core Processor, 32 gb ram, with a NVIDIA GeFoerceRTX2070 super graphics card, the two monitors are Display port out of the card and HDMI into the monitors, USB is power and touch.
How do I keep the right screen from moving to the left when I run ED?

 

[Bionic Bytes]

Hi BB.
I just got the CD latest release and installed per your user's manual. Almost everything is going as described. The issue I am having is when I make ED go full screen, it moves one display to the right and one display disappears. I have 3 monitors total, main is a 75" TV, the other two are 7" touch screens in my sim pit, upper L & R, I am running an AMD Ryzen 7 3800X 8-Core Processor, 32 gb ram, with a NVIDIA GeFoerceRTX2070 super graphics card, the two monitors are Display port out of the card and HDMI into the monitors, USB is power and touch.
How do I keep the right screen from moving to the left when I run ED?

Many thanks for your support.
From what you say (MFD Windows are repositioning them selves) this is by design when the application has detected that one of the windows is out of bounds when placed onto a monitor.
Even if 1 pixel extended beyond the monitor boundary, it will reposition. It does this so that you don't "loose" a window on a monitor which is no longer attached, etc.
Sometimes, the thickness of the windows borders is under reported (by windows API) and what we think is in side the monitor boundary is in fact extending beyond. So the simple solution is to absolutely ensure the monitor is positioned wholey with in a monitor boundary. You can do this by positioning and resizing the windows, as you have been doing, just don't stretch them to the very edges - leave a gap and refine/tweak until you reach the limits.
The other way, is to close MFDCougar and then manually edit MFD.ini so that the WindowX,WindowY,WindowWidth,WindowHeight parameters are what you want them to be (as well as the ViewPort parameters).

 

[JetMac4Life]

Hi BB.
Thank you very much for your reply.
I will give it try!!

O7
CMDR ReaperKeeper

 

[JetMac4Life]

Many thanks for your support.
From what you say (MFD Windows are repositioning them selves) this is by design when the application has detected that one of the windows is out of bounds when placed onto a monitor.
Even if 1 pixel extended beyond the monitor boundary, it will reposition. It does this so that you don't "loose" a window on a monitor which is no longer attached, etc.
Sometimes, the thickness of the windows borders is under reported (by windows API) and what we think is in side the monitor boundary is in fact extending beyond. So the simple solution is to absolutely ensure the monitor is positioned wholey with in a monitor boundary. You can do this by positioning and resizing the windows, as you have been doing, just don't stretch them to the very edges - leave a gap and refine/tweak until you reach the limits.
The other way, is to close MFDCougar and then manually edit MFD.ini so that the WindowX,WindowY,WindowWidth,WindowHeight parameters are what you want them to be (as well as the ViewPort parameters).

BB.

I am sorry to say that I have tried everything I know to get the windows inside the monitor area, I have had them all at one inch sq. It makes no difference, the MFD Windows are repositioning them selves still.
I am not computer savvy enough to know what the correct parameters are for editing the INI file.
Is there any way that you can still help? Can I send you some sort of log file?
I am really lost and in need of help.

Many Thanks.
ReaperKeeper.

 

[Bionic Bytes]

BB.

I am sorry to say that I have tried everything I know to get the windows inside the monitor area, I have had them all at one inch sq. It makes no difference, the MFD Windows are repositioning them selves still.
I am not computer savvy enough to know what the correct parameters are for editing the INI file.
Is there any way that you can still help? Can I send you some sort of log file?
I am really lost and in need of help.

Many Thanks.
ReaperKeeper.

There are some logs files in the LOGS folder that you could zip and send to me.
Also you could include your MFD.ini file too, plus a photo of how your monitors are positioned (the windows monitor arrangement would be good)

 

[JetMac4Life]

There are some logs files in the LOGS folder that you could zip and send to me.
Also you could include your MFD.ini file too, plus a photo of how your monitors are positioned (the windows monitor arrangement would be good)

Many Thanks for your help!