Anyone know how to use RTT Client/Server in 4.35 for the MFDS?
-
This is disabled in code and does nothing.
Well explain how it fixed MFDs from displaying HUD data for so many.
-
Well explain how it fixed MFDs from displaying HUD data for so many.
Because they use MFDE 0.6.3.0 build and compiled not from the latest source code.
To identify: If MFDE has the option for Left Right 3rd 4th MFD it’s the older version which determine the size to use internally in the app by reading the BMS config for the doubleresolution parameter. As in 4.35 this parameter is not used anymore and therefore not present MFDE reads null and defaults that to 0 hence sets internally the resolution of the Texture to 600x600 but get a Texture of 1200x1200.Hence this version shows part of the HUD. And by adding doubleresolution to BMS config forces this version to assume a Texture resolution of 1200x1200. The parameter itself has no effect in BMS itself.
As of 4.35 the exported Texture Resolution is fixed to 1200x1200MFDE 0.6.3.0 build from the latest source on github does not read the doubleresolution anymore but reads the real dimension from the texture directly from the memory
Gesendet von meinem SM-G930F mit Tapatalk
-
Because they use MFDE 0.6.3.0 build and compiled not from the latest source code.
To identify if MFDE has the option for Left Right 3rd 4th MFD it’s the older version which determine the size to use internally in the app by reading the BMS config for the doubleresolution parameter. As in 4.35 this parameter is not used anymore and therefore not present MFDE reads null and defaults that to 0 hence sets internally the resolution of the Texture to 600x600 but get a Texture of 1200x1200.Hence this version shows part of the HUD. And by adding doubleresolution to BMS config forces this version to assume a Texture resolution of 1200x1200. The parameter itself has no effect in BMS itself.
As of 4.35 the exported Texture Resolution is fixed to 1200x1200MFDE 0.6.3.0 build from the latest source on github does not read the doubleresolution anymore but reads the real dimension from the texture directly from the memory
Gesendet von meinem SM-G930F mit Tapatalk
Thank you that is my point. Saying it does nothing without your explanation will make people think it does not solve the MFD HUD problem. It does. That is all.:)
-
Saying it does nothing without your explanation will make people think it does not solve the MFD HUD problem. It does. That is all.:)
It is VERY very simple,
BMS-Technical-Manual.pdf
page 167 (13-167)
13.10 Options removed from 4.35
g_bDoubleRTTResolution Obsolete as it is managed with RTT options
That is all.
(Although IT IS stated in this forum on other support threads at least twice last days by BMS Devs)
But if again it DOES fix stuff after these… :yo:
-
Send you a PM.
-
It is VERY very simple,
BMS-Technical-Manual.pdf
page 167 (13-167)
13.10 Options removed from 4.35
g_bDoubleRTTResolution Obsolete as it is managed with RTT options
That is all.
(Although IT IS stated in this forum on other support threads at least twice last days by BMS Devs)
But if again it DOES fix stuff after these… :yo:
as stated in various threads even so the g_bDoubleRTTResolution is obsolete for BMS itself no doubt about that.
It’s not OSBOSELTE for some of the 3rd party display extraction tools as they still use g_bDoubleRTTResolution to determine the the size of the texture in memory and therefore either need to updated or have the g_bDoubleRTTResolution 1 in the 4.35 BMS config as this forces the 3rd party tool to use 1200x1200 for the expected texture size.
Example the current version that is downloadable from https://github.com/lightningviper/lightningstools#mfdextractor still uses the value
namespace F4Utils.SimSupport { public interface IDoubleResolutionRTTChecker { bool IsDoubleResolutionRtt { get; } } public class DoubleResolutionRTTChecker : IDoubleResolutionRTTChecker { private readonly IBMSConfigFileReader _bmsConfigFileReader; public DoubleResolutionRTTChecker(IBMSConfigFileReader bmsConfigFileReader = null) { _bmsConfigFileReader = bmsConfigFileReader ?? new BMSConfigFileReader(); } public bool IsDoubleResolutionRtt { get { return _bmsConfigFileReader.ConfigLines.Select(Util.Tokenize) .Where(tokens => tokens.Count > 2) .Any( tokens => tokens[0].ToLowerInvariant() == "set" && string.Equals(tokens[1], "g_bDoubleRTTResolution", StringComparison.InvariantCultureIgnoreCase) && string.Equals(tokens[2], "1", StringComparison.InvariantCultureIgnoreCase)); } } } }
in the latest Master source code this has been replaced but the latest Master has not been build and made available for Enduser download. Only if you pull the repo and build the exe yourself you get the latest code changes wich in fact don’t rely on g_bDoubleRTTResolution hence work with 4.35 out of the box
So for MFDE if your MFD & HUD Options looks as on 1 left side add g_bDoubleRTTResolution 1 to your 4.35 falcon bms.cfg if it looks like 2 on the right side you don’t need to add it
-
It is VERY very simple,
BMS-Technical-Manual.pdf
page 167 (13-167)
13.10 Options removed from 4.35
g_bDoubleRTTResolution Obsolete as it is managed with RTT options
That is all.
(Although IT IS stated in this forum on other support threads at least twice last days by BMS Devs)
But if again it DOES fix stuff after these… :yo:
It IS simple. It does DO something and NOT NOTHING like you said. :yo:
-
It IS simple. It does DO something and NOT NOTHING like you said. :yo:
Cool then, ask devs (RedDog?) for BMS-Technical-Manual.pdf update to correct this, I was just passing official info directly from there as and previous posts about this line effectiveness in RTT, which was the original thread question.
Although I have MFDE I’ve stopped using it some 4y+ since playing with Yame and RTT.
-
Cool then, ask devs (RedDog?) for BMS-Technical-Manual.pdf update to correct this, I was just passing official info directly from there as and previous posts about this line effectiveness in RTT, which was the original thread question.
Although I have MFDE I’ve stopped using it some 4y+ since playing with Yame and RTT.
I am not asking devs to do anything. Reread oakdesigns post here if you are having trouble understanding that it is disabled but still has effect on MFDE: https://www.benchmarksims.org/forum/showthread.php?40994-Anyone-know-how-to-use-RTT-Client-Server-in-4-35-for-the-MFDS&p=561034&viewfull=1#post561034
-
Thanks for suggesting this Icarus - I now have MFDees! But do they stay unfrozen or not?… that is the question
-
Thanks for suggesting this Icarus - I now have MFDees! But do they stay unfrozen or not?… that is the question
Not until U1
-