Ice’s Falcon BMS Profile Updated for BMS 4.37
-
IIRC CPD requires the map to be 4096x4096
-
IIRC CPD requires the map to be 4096x4096
Thx Oak, that explains that!! Whoever saved\Made that map saved it with every object showing, which is a mess. I just removed everything but airbases and will try it…
-
Linknet, can you tell me how the profile defines the CPD Map coordinates (and where it pulls the map from)? I would like to use this 2048x2048 map for the MidEast128 theater but it lands on the Map Display incorrectly. I was able to get it into WDP and MC, but all I see is the NE corner in the CPD… Normally the Map (which I am now editing in MC, is 4096x4096…
Map size 4096x4096 pixels
64 segment map: Bottom Left Corner 0,0 feet Top Right Corner 3359580, 3359580 feet (1024,1024 km)
128 segment map: Bottom Left Corner 0,0 feet Top Right Corner 6719160, 6719160 feet (2048, 2048 km)
Have fun
-
Map size 4096x4096 pixels
64 segment map: Bottom Left Corner 0,0 feet Top Right Corner 3359580, 3359580 feet (1024,1024 km)
128 segment map: Bottom Left Corner 0,0 feet Top Right Corner 6719160, 6719160 feet (2048, 2048 km)
Have fun
How are you calculating X Y for 128 seg. As BMS is not using real live 3280.84 but 3279.98
So the max values on a 128 seg should be 6717399Gesendet von meinem SM-G930F mit Tapatalk
-
Map size 4096x4096 pixels
64 segment map: Bottom Left Corner 0,0 feet Top Right Corner 3359580, 3359580 feet (1024,1024 km)
128 segment map: Bottom Left Corner 0,0 feet Top Right Corner 6719160, 6719160 feet (2048, 2048 km)
Have funThanks, I somehow got the map I want to display properly and my plane position and Steerpoints are correct.
-
How are you calculating X Y for 128 seg. As BMS is not using real live 3280.84 but 3279.98
So the max values on a 128 seg should be 6717399Gesendet von meinem SM-G930F mit Tapatalk
Where on earth did they get their conversion factor from?
Thanks for the information. That means an error of 1761 ft at the top right corner for the 128 segment map and half that at the centre, it’s too late to change all the map scaling or more correctly I don’t want to revisit that part of the profile. From my very rough calculations on the 30Nm map scale and with the current size of the CPD the error’s around 3 pixels at the topmost corner on a 1920x1080 screen and half that in the centre. So you really won’t notice it. If I ever revisit the CPD I’ll use the figures you supplied.
On the 30Nm scale map the aircraft image itself is around 3Nm x 3Nm which actually surprised me since I had never calculated it before.
-
Where on earth did they get their conversion factor from?
Thanks for the information. That means an error of 1761 ft at the top right corner for the 128 segment map and half that at the centre, it’s too late to change all the map scaling or more correctly I don’t want to revisit that part of the profile. From my very rough calculations on the 30Nm map scale and with the current size of the CPD the error’s around 3 pixels at the topmost corner on a 1920x1080 screen and half that in the centre. So you really won’t notice it. If I ever revisit the CPD I’ll use the figures you supplied.
Never tried to dig why 3279.98 is used but it’s a fact that it is.
As I’m creating overlays for Tacview to show runways and ILS cones I need to be within max 5 feet deviation in my calculations as in full zoom in Tacview and an larger offset the AC would land left or right instead of on the runwayGesendet von meinem SM-G930F mit Tapatalk
-
As a last resort can you download this DataAutoUpdate.exe and temporarily replace the one in the C:\Bin folder with this one.
https://www.mediafire.com/file/qyt4gwwt6rnueui/DataAutoUpdate.exe/file
It should just dump the Auto_Left.png and Auto_Right.png in the C:\Bin folder, they won’t show in the profile, then see if these are updating.
…the left and right files are copied into BIN folder without data / update (empty) on it. …Probably I have to live with it and have to use the other kneeboard…
-
…the left and right files are copied into BIN folder without data / update (empty) on it. …Probably I have to live with it and have to use the other kneeboard…
If you can let me have a copies of your briefing.ini and callsign.ini files I’ll check them out.
I think you can include them in a zip file on here or send the zip in a PM.
-
Have problem with Helios V 1.6.3504.0001/V435-8.
Started Falcon 4.35 U2 TE in
2d World, briefing - executed print and Datacard save.
Continued with start Helios Control Center, however in CPD&MAP the steerpoints of a older TE are still active .
MapOverlay_15; MapOverlay_30; MapOverlay_60, has the wrong lines and waypoints from an older TE. Will not be updated.All ok with MFD steerpoints, thread circles, etc. of active TE are visible.
Kindly ask for tip or solution how to correct this problem.Greetings….NIK
-
@nik:
Have problem with Helios V 1.6.3504.0001/V435-8.
Started Falcon 4.35 U2 TE in
2d World, briefing - executed print and Datacard save.
Continued with start Helios Control Center, however in CPD&MAP the steerpoints of a older TE are still active .
MapOverlay_15; MapOverlay_30; MapOverlay_60, has the wrong lines and waypoints from an older TE. Will not be updated.
Greetings….NIKMaybe you didn’t do this:
If you did complete the above step then try this:
1. Start BMS and load a TE and print the briefing and save the DTC then exit BMS. Don’t start Control Center.
2. Delete MapOverlay_15.png; MapOverlay_30.png; MapOverlay_60.png
3. In C:\Bin rename PathNames.ini to PathNames.bak or something similar so you can restore it later.
4. In C:\Bin\Briefing delete Briefing.txt
5. Now manually run C:\Bin\DataAutoUpdate.exe which should run as a process and exit after about 10 seconds.
6. Now check that the newly created C:\Bin\PathNames.ini has all the correct pathnames, callsign etc. for your system.
7. Now check that the newly created C:\Bin\Briefing.txt has the latest TE data.
8. Now check that the newly created MapOverlay_15.png; MapOverlay_30.png; MapOverlay_60.png have the latest TE waypoints.
9. Restore the original C:\Bin\PathNames.ini
Let me know the results.
-
Thank you for the help, but unfortunately to no avail.
Did all the steps exactly.5. Now manually run \ Bin \ DataAutoUpdate.exe which should run as a process and exit after about 10 seconds. nothing, but UpdatePathNames.exe will update both files.
8. Now check that the newly created MapOverlay_15.png; MapOverlay_30.png; MapOverlay_60.png have the latest TE waypoints.
MapOverlay_15 / 30/60 were not regenerated.
best regards Nik
different flight paths
-
So just to confirm, after manually running DataAutoUpdate.exe the PathNames.ini file which was deleted was not recreated.
If that’s the case then for some reason DataAutoUpdate.exe isn’t running at all since it will recreate PathNames.ini even if the registry entries and/or it can’t find the BMS path.
So that’s where the problem is.
Maybe it’s corrupt or stuck in memory.
Do a reboot. Delete the C:\Bin folder and restore it from the download and delete the PathNames.ini file. Then just manually run the DataAutoUpdate.exe again. It should recreate the PathNames.ini file no matter what.
-
DataAutoUpdate it was stuck in memory and works now.
But sometimes Path & Lines works and sometimes it doesn’t. Anyway, I live with it now, it takes too much time to look for the fault.
Many Thanks
-
Wonder if somehow you don’t have the latest DataAutoUpdate.exe? I know earlier versions (mine anyway) had a memory issue and just kept using more and more memory until you killed the process… This was fixed later on.
-
Dear comrades I have a stupid question here: My BMS is running on the same monitor as my Helios touchscreen …… How could I force it to run on the secondary 4K monitor ? I’ve tried dragging in windowed mode but as soon as I go fullscreen it jumps back to the smaller touchscreen which is set as main …
EDIT: Disregard. I’ve even tried the TVGameLauncher but to no avail, until I found out there is actually an option in the Graphic section of the Falcon BMS in game setting, to choose the output display. A simple choice and the tour est joué
Thx for this awesome setup!! Flying now is much more productive with Helios setup and the inclusion of radio commands is such a relieve !!! No more bending over and looking for keys on the keyboard anymore !!
And also are the side panels supposed to be touchable? My ICP and MFD keys all worked on the touchscreen but not most of the buttons on the side panel.
-
And also are the side panels supposed to be touchable? My ICP and MFD keys all worked on the touchscreen but not most of the buttons on the side panel.
There aren’t any side panels in the latest versions of the Ice Profile. there’s a combined console, is that what’s not working?
-
Thx for the quick reply Link, Yes I checked the first page again and that’s how you called it, the combined console. I’m trying to do a ramp start from there but most of the switch when I touch them they doesn’t react. However I could click on them in the 3D cockpit with the mouse. And I’m just starting out, I’m trying as well to see what I can find.
-
Thx for the quick reply Link, Yes I checked the first page again and that’s how you called it, the combined console. I’m trying to do a ramp start from there but most of the switch when I touch them they doesn’t react. However I could click on them in the 3D cockpit with the mouse. And I’m just starting out, I’m trying as well to see what I can find.
Sound like a keyfile issue, did you work through all of the steps in the SetUp Guide which comes with the download?
All of the switches, knobs etc. should work if you get it set up correctly.
-
I think so too, because I was just using the default Warthog key profile and made some changes, but when you said copy my own over I didn’t know which one is the current one so I just used the default Ice key file. While flying around I also found out that only the axis of my input were intact, all the buttons are gone. TMS, DMS, trim etc, none of them works anymore. So I’ll compare the warthog one with Ice’s and copy over the rest, I’ll see how that goes. Thx in advance !!