<p>@kungfoo<strong> - thank you for this app. It is great, simple and just works!!</strong><br /><br />Thank you.</p>
Posts made by walkman
-
RE: New free MFD/ICP app to control Falcon BMS from touch devices
-
RE: YAME64 suite
Yes, g_bExportRTTTexture are set to 1 in 4.34 and 4.33, and there are no 3DHook dll files in the x64 folder that I am seeing. See Pics below:
And yes, the simple test of the ADI and Altimeter gauges works. I was surprised that they did.
The only problem appears to be that the MFDs, DED, and RWR symbology are not displaying. I have blacked out extractions for those displays.
Anybody have any suggestions? Help is greatly appreciated to solve this issue.
-
RE: YAME64 suite
Ok, seems all good. So please double check if the g_bExportRTTTexture is set to 1 in your falcon bms.cfg.
As a simple test, other gauges (like an altitude or ADI) do work?Yes, g_bExportRTTTexture are set to 1 in 4.34 and 4.33, and there are no 3DHook dll files in the x64 folder that I am seeing. See Pics below:
And yes, the simple test of the ADI and Altimeter gauges works. I was surprised that they did.
The only problem appears to be that the MFDs, DED, and RWR symbology are not displaying. I have blacked out extractions for those displays.
-
RE: YAME64 suite
I was referring to YAME configuration file, not Falcon.
My bad, the file is called YAME64.xml and should be located in conf folder of the yame installation path.
I can’t remember well as it is now all different…Here is a pic of my YAME64.xml. I could not figure out how to attach the file to this message.
Again, thanks for the help.
-
RE: YAME64 suite
Yes that is correct. There is no 3Dhook dll in the Falcon BMS 4.34/Bin/x64 folder, and the set g_bExportRTTTexture is set to 1 in the 4.33 and 434 falcon_bms.cfg file.[/QUO
Please, s3nd me your config.xml file
I am unsure where I can find this related file. Can you direct me to where I can find the config.xml file you are referring to. When I did a global search on Drive C for config.xml, these are the files that were retrieved.
Thank you for your help.
-
RE: YAME64 suite
Sure 4.34 does not contain the 3Dhook dll anymore and rttexport is set to 1?
Yes that is correct. There is no 3Dhook dll in the Falcon BMS 4.34/Bin/x64 folder, and the set g_bExportRTTTexture is set to 1 in the 4.33 and 434 falcon_bms.cfg file. Thanks for responding. Any further suggestions from anyone would be much appreciated.
-
RE: YAME64 suite
All good now. I reinstalled BMS for the third time and the displays extract as designed. Thanks to all that gave input.
Not so fast…I thought it was fixed, however I was using 4.33 when it was working. Realizing this, I changed to 4.34 and the extraction is still blacked out. So I’m back with the same issue. Any suggestions?
-
RE: YAME64 suite
I managed to get the YAME Client to start with the extracted screen to display on my second monitor (see picture below) but when I start to fly with BMS 4.34 the MFD, DED and RWR symbology is not extracted. The extraction remains blacked out. I’ve tried to reinstall YAME again and got the same results. Does anyone have any suggestions on how I can resolve this?
All good now. I reinstalled BMS for the third time and the displays extract as designed. Thanks to all that gave input.
-
RE: YAME64 suite
I can not get YAME 64 v1.2 to work on my Win 10 PC. Previously I had it working with BMS 4.34 but my windows crashed (for other reasons) so I reinstalled Win 10 on a reformatted drive. I then loaded BMS 4.33 U1-U5, BMS 4.34, and YAME64 v1.2. I also installed MS Visual C++ as shown bellow:
When I launch YAME, this is how it starts:
The Global tab is blank and looks like this:
When I start the Client I get this error message:
However, both Falcon BMS.cfg files in 4.33 U1 and 4.34 are set to 1 as shown below:
I also made sure the Registry was changed to C:\Falcon BMS 4.34 as shown below:
Additionally, the YAME64.xml path is set to the correct location as shown below:
The YAME log file looks like this:
At this point, I am not sure what to do. I tried to uninstall all versions of BMS and YAME64 v1.2, and then reinstalling them with no change in failure.
Again, I previously had YAME64 v1.2 running great with BMS 4.34 before my Win 10 crashed hard, forcing me to reinstall Win 10 on a reformatted drive. So I know my PC is totally compatible. I am thinking it is some setting or .cfg that is not correct, but I am unable to locate it. I followed the How-to from the YAME web site with regards to the v1.2 workaround and BMS 4.34.
I’m not sure what to do next. Any help would be much appreciated. Thank you.
I managed to get the YAME Client to start with the extracted screen to display on my second monitor (see picture below) but when I start to fly with BMS 4.34 the MFD, DED and RWR symbology is not extracted. The extraction remains blacked out. I’ve tried to reinstall YAME again and got the same results. Does anyone have any suggestions on how I can resolve this?
-
RE: YAME64 suite
I can not get YAME 64 v1.2 to work on my Win 10 PC. Previously I had it working with BMS 4.34 but my windows crashed (for other reasons) so I reinstalled Win 10 on a reformatted drive. I then loaded BMS 4.33 U1-U5, BMS 4.34, and YAME64 v1.2. I also installed MS Visual C++ as shown bellow:
When I launch YAME, this is how it starts:
The Global tab is blank and looks like this:
When I start the Client I get this error message:
However, both Falcon BMS.cfg files in 4.33 U1 and 4.34 are set to 1 as shown below:
I also made sure the Registry was changed to C:\Falcon BMS 4.34 as shown below:
Additionally, the YAME64.xml path is set to the correct location as shown below:
The YAME log file looks like this:
At this point, I am not sure what to do. I tried to uninstall all versions of BMS and YAME64 v1.2, and then reinstalling them with no change in failure.
Again, I previously had YAME64 v1.2 running great with BMS 4.34 before my Win 10 crashed hard, forcing me to reinstall Win 10 on a reformatted drive. So I know my PC is totally compatible. I am thinking it is some setting or .cfg that is not correct, but I am unable to locate it. I followed the How-to from the YAME web site with regards to the v1.2 workaround and BMS 4.34.
I’m not sure what to do next. Any help would be much appreciated. Thank you.
-
RE: UHF OFF even after DTC Load. Need Help with Comms.
UHF radio to Main or Both (Main + Guard) position? (to power up the radio)
….
Yes, the radio is in Main. But also tried Both. Still UHF OFF. Going to reinstall 4.33 U5. The problem seem to appear soon after I did the update the other day.
-
RE: UHF OFF even after DTC Load. Need Help with Comms.
im guessing you have to switch the CNI knob to UFC
Yes, I have the CNI knob selected to UFC, but it still says UHF OFF on the DED.
-
UHF OFF even after DTC Load. Need Help with Comms.
I am having some issue with my UHF as it comes up from the start in OFF mode and I can’t get it to turn on. Even after I do a DTC Load, it’s still OFF. My Data Cartridge presets 1-14 are set to the original freq’s. Preset 15 is set to tower and is selected as Default. I did notice that I have a preset 0 set to freq 000.000. I am wondering if I should even have a preset 0, and if not how to get rid of it. Could this be my problem? Much appreciate any help with this. Thanks.
-
RE: Flounder's X52 Pro Keyfile/DX Profile for BMS 4.33
Operator Error in this instance - the WARN RESET on the ICP doesn’t extinguish the MASTER CAUTION light - it clears the WARN message from the HUD. You depress the MC light directly to do it. If it doesn’t extinguish it due to damage to other systems, it can be done via the ELEC panel. The Dash-1 manual does a good job of explaining all this far better than I can.
Roger That!! Thanks - Remove & Replace Operator - Lol.
-
RE: Flounder's X52 Pro Keyfile/DX Profile for BMS 4.33
It’s been quite some time since I’ve worked with them closely, but there should be no functional difference. The difference should be that the ‘full’ keyfile has the full list of available commands included, with many un-mapped (no key assigned … "0XFFFFFFFF "). The ‘non-full’ should only include the mapped keys … i.e., not all the commands, but whatever is included is mapped.
I normally recommend using the “full” keyfile so if you want to add something the command is there and it’s just a matter of mapping it.
Here are the commands from the non-full:
SimDriftCO 121 0 0x4E 0 0 0 1 “ICP-Drift C/O Toggle”
SimWarnReset 115 0 0x4E 1 0 0 1 “ICP-Warning reset”And here are the commands from the ‘full’ keyfile (inactive commands greyed out):
SimDriftCO 121 0 0x4E 0 0 0 1 “ICP: DRIFT C/O Switch - Tog. ON/NORM!”
SimDriftCOOn 121 0 0XFFFFFFFF 0 0 0 1 “ICP: DRIFT C/O Switch - ON”
SimDriftCOOff 121 0 0XFFFFFFFF 0 0 0 1 “ICP: DRIFT C/O Switch - NORM”
SimWarnReset 115 0 0x4E 1 0 0 1 “ICP: DRIFT C/O Switch - WARN RESET”They look the same to me. ??
Roger that! I believe the problem may be with the F4BMS 4.33 U4 game itself since selecting the WARN RESET switch from the 2D or 3D cockpit view has no effect with extinguishing the MASTER CAUTION light, or I might just have a poor understanding of the WARN RESET switch functionality.
-
RE: Flounder's X52 Pro Keyfile/DX Profile for BMS 4.33
What is the delta between these two .key files? Which .key file is represented by the included .jpg images from the zip file? Are the ICP buttons mapped differently between the two .key files? I am currently using Flounder X52 Pro v5.key and all functions work great, except for one. I can’t seem to get the “ICP Drift c/o Warn” to work by pressing the Shift + NumPadSum keys. All other ICP and MFD keys work flawlessly. Any help would be appreciated. Thanks.
-
RE: Flounder's X52 Pro Keyfile/DX Profile for BMS 4.33
The part that matters for knowing it is the Fire C button is the button number, bolded above. In the keyfile they run from DX 0 - 31, so there’s an ‘offset’ of one … Button 1 is DX 0, button 2 is DX 1, etc. So we’re looking for DX 4, which is button 5. Match that to the button map for the HOTAS:
https://farm5.staticflickr.com/4397/36801125755_81f02405db_b.jpg
Got it. Thanks!!!
-
RE: Flounder's X52 Pro Keyfile/DX Profile for BMS 4.33
This is how you would change one command to another, using the request above as an example. First open the keyfile in notepad or any other plain text editor. It should be “x:\Falcon BMS 4.33 U1\User\Config\Flounder X52 Pro v5 - Full.key” unless the user renamed it.
Go toward the bottom of the keyfile and find the DX commands. This section:
#=================================================================================== #================================================================================== SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 "========= HOTAS UNSHIFTED =========" SimTriggerFirstDetent 0 -1 -2 0 0x0 -1 SimPickle 1 -1 -2 0 0x0 -1 RecenterTrackIR 2 -1 -2 0 0x0 -1 SimMissileStep 3 -1 -2 0 0x0 -1 PrettyScreenShot 4 -1 -2 0 0x0 -1 SimHotasPinkyShift 5 -1 -2 0 0x0 -1 AFBrakesToggle 6 -1 -2 0 0x0 -1 SimToggleMissileCage 7 -1 -2 0 0x0 -1 SimArmMasterArm 8 -1 -2 0 0x0 311 SimSafeMasterArm 9 -1 -2 0 0x0 311 SimExtlMasterNorm 10 -1 -2 0 0x0 115 SimExtlMasterOff 11 -1 -2 0 0x0 115 AFGearUp 12 -1 -2 0 0x0 119 AFGearDown 13 -1 -2 0 0x0 118 SimTriggerSecondDetent 14 -1 -2 0 0x0 -1 SimCursorEnable 15 -1 -2 0 0x0 -1 SimRadarRangeStepDown 16 -1 -2 0 0x0 -1 SimRadarRangeStepUp 17 -1 -2 0 0x0 -1 SimRFNorm 18 -1 -2 0 0x0 310 SimTMSUp 19 -1 -2 0 0x0 -1 SimTMSRight 20 -1 -2 0 0x0 -1 SimTMSDown 21 -1 -2 0 0x0 -1 SimTMSLeft 22 -1 -2 0 0x0 -1 SimTransmitCom1 23 -1 -2 0 0x0 -1 SimCommsSwitchRight 24 -1 -2 0 0x0 -1 SimTransmitCom2 25 -1 -2 0 0x0 -1 SimCommsSwitchLeft 26 -1 -2 0 0x0 -1 SimSelectMRMOverride 27 -1 -2 0 0x0 -1 SimDeselectOverride 28 -1 -2 0 0x0 -1 SimSelectSRMOverride 29 -1 -2 0 0x0 -1 SimDoNothing 30 -1 -2 0 0x0 -1 AWACSDeclare 31 -1 -2 0 0x0 -1 SimDMSUp 0 -1 -3 0 0x0 -1 SimDoNothing 0 -1 -3 1 0x0 -1 SimDMSRight 0 -1 -3 2 0x0 -1 SimDoNothing 0 -1 -3 3 0x0 -1 SimDMSDown 0 -1 -3 4 0x0 -1 SimDoNothing 0 -1 -3 5 0x0 -1 SimDMSLeft 0 -1 -3 6 0x0 -1 SimDoNothing 0 -1 -3 7 0x0 -1 #================================================================================== SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 "========= HOTAS SHIFTED =========" SimWheelBrakes 256 -1 -2 0 0x0 -1 SimEmergencyJettison 257 -1 -2 0 0x0 123 ReloadTrackIR 258 -1 -2 0 0x0 -1 SimCATSwitch 259 -1 -2 0 0x0 115 AFResetTrim 260 -1 -2 0 0x0 -1 SimHotasPinkyShift 261 -1 -2 0 0x0 -1 SimCBEOSB_6L 262 -1 -2 0 0x0 126 SimCBEOSB_8L 263 -1 -2 0 0x0 126 SimLaserArmOn 264 -1 -2 0 0x0 310 SimLaserArmOff 265 -1 -2 0 0x0 310 SimAVTRSwitchOn 266 -1 -2 0 0x0 115 SimAVTRSwitchOff 267 -1 -2 0 0x0 115 SimFuelDoorOpen 268 -1 -2 0 0x0 311 SimFuelDoorClose 269 -1 -2 0 0x0 311 SimDoNothing 270 -1 -2 0 0x0 -1 SimRadarCursorZero 271 -1 -2 0 0x0 -1 SimHSDRangeStepDown 272 -1 -2 0 0x0 -1 SimHSDRangeStepUp 273 -1 -2 0 0x0 -1 SimRFQuiet 274 -1 -2 0 0x0 310 SimCMSUp 275 -1 -2 0 0x0 -1 SimCMSRight 276 -1 -2 0 0x0 -1 SimCMSDown 277 -1 -2 0 0x0 -1 SimCMSLeft 278 -1 -2 0 0x0 -1 SimRadarBarScanChange 279 -1 -2 0 0x0 -1 SimRadarAzimuthScanChange 280 -1 -2 0 0x0 -1 SimRadarBarScanChange 281 -1 -2 0 0x0 -1 SimRadarAzimuthScanChange 282 -1 -2 0 0x0 -1 SimSelectMRMOverride 283 -1 -2 0 0x0 -1 SimDeselectOverride 284 -1 -2 0 0x0 -1 SimSelectSRMOverride 285 -1 -2 0 0x0 -1 SimDoNothing 286 -1 -2 0 0x0 -1 AWACSVectorToThreat 287 -1 -2 0 0x0 -1 AFElevatorTrimUp 2 -1 -3 0 0x0 -1 SimDoNothing 2 -1 -3 1 0x0 -1 AFAileronTrimRight 2 -1 -3 2 0x0 -1 SimDoNothing 2 -1 -3 3 0x0 -1 AFElevatorTrimDown 2 -1 -3 4 0x0 -1 SimDoNothing 2 -1 -3 5 0x0 -1 AFAileronTrimLeft 2 -1 -3 6 0x0 -1 SimDoNothing 2 -1 -3 7 0x0 -1
In that section of the keyfile, you want to change this line:
PrettyScreenShot 4 -1 -2 0 0x0 -1
What you want to do is change the command (“PrettyScreenShot”). In this example to this command (also found in the keyfile), “SimCBEOSB_3L”
Just cut/paste so that “PrettyScreenShot 4 -1 -2 0 0x0 -1” becomes “SimCBEOSB_3L 4 -1 -2 0 0x0 -1”
Then re-save the key file.
That’s Awesome!!! Is there a doc that explains what the codes represent for the varies HOTAS buttons and keyboard keys? In other words, how would I have known that “….4 -1 -2 0 0x0 -1” is for the Fire C button? Regardless, thanks again for the quick and informative response.
-
RE: Flounder's X52 Pro Keyfile/DX Profile for BMS 4.33
I’m more that happy to help you remap a more useful command to replace ‘pretty screen shot’, but FOV norm/expand already exists. It is the pinky switch (DX Button #5). The way it works is …. on short press (about 1/4 second) it will act to change FOV on the current sensor of interest (SOI).
So on AA FCR, NORM/EXP; on AG NORM/EXP/DBS1/DBS2; on TGP WIDE/NARO; on WPN NORM/EXP.
When held the pinky then acts as a shift key for additional ‘shifted commands’.
So tap the pinky for SOI FOV change and hold the pinky for the shift layer function.
Thanks for the quick reply. That’s great. I didn’t know that function was already there. I will check it out later tonight.