MFDE not saving position after replacing monitor***SOLVED***
-
@Icarus Ok, I deleted that, and same thing is happening.
I open MFDE, recover Gauges, Drag and drop, Click OK ,and or apply on MFDE
window and they all disappear.
Mud -
@MudDog Well then there is something not right on your computer. Do you have same bms resolution as your windows setting? Registry issue? Works fine on all my computers. Do you have the proper NetFramework etc installed that github says you need to run it?
-
@Icarus I don’t know. I’ve had this working for years and all’s I did was swap displays. but i feel like its had windows updates. maybe something changed??
-
@MudDog Make sure you have Visual Studio 2022 Community Edition
and .NET Framework 4.8 installed. Thats all I can think of. Also make sure that config fole is not read only. -
@Icarus checked all that. good to go.
i am at a loss. thanks for your help though. -
any other suggestions?
-
@MudDog My friend Homer has the same problem…we are also looking for a solution.
-
I have been away for about 2 years but consider myself someone with some expertise on MFDE. Have you had a look into you user.config files as it’s basically a human readable file. It might be that the display detection (MFDE relys in Windows here) might get messed up. That might be fixed by setting the display assignment in the config manually with a text editor
-
@MudDog
haven’t the time to look into the code what has changed since I left BMS 2 years ago. But if it’s still the same concept of storing positions you could do the following.
position your gauges as you want them, before clicking ok save a copy of the user.config. After clicking ok compare the previously saved copy with the one after you forcefully saved in MFDE. IIRC the positioning is written to the config after every drag and drop and not only after saving from the MFDE UI by clicking ok. Could be a first hint to check if both versions differ let me know. Maybe if have some time in the next few days to look what has been changed between 6.3 which I’m familiar with to code and 6.4. Having a look into the log.txt which is stored in the same %appdata%/local/MFDExtractor folder might be useful -
Found my problem, Main screen was set at 150% scale.
I changed to 100% and MFDE works like it should again.
thank you!
Mud