Ice’s Falcon BMS Profile Updated for BMS 4.37
-
Helios vs RTT extraction:
I noticed choppy MFD FRC extraction when using linknet’s profile, and at first I thought I’d have to live with that because of the set g_nRTTExportBatchSize 2 limit as it stands now. Playing around with VSync or monitor refresh rates didn’t solve the issue either. Yesterday, I tried running RTT Client (without the profile loaded) and it is MUCH smoother, even with FPS set to 30 in the RTT config file. Will try again tonight, removing the Helios extracted MFDs and replacing them with RTT MFDs. Not ideal, because yet another app will be running, but I also feel a smooth running FCR is important in A/A combat situations.
-
Helios vs RTT extraction:
I noticed choppy MFD FRC extraction when using linknet’s profile, and at first I thought I’d have to live with that because of the set g_nRTTExportBatchSize 2 limit as it stands now. Playing around with VSync or monitor refresh rates didn’t solve the issue either. Yesterday, I tried running RTT Client (without the profile loaded) and it is MUCH smoother, even with FPS set to 30 in the RTT config file. Will try again tonight, removing the Helios extracted MFDs and replacing them with RTT MFDs. Not ideal, because yet another app will be running, but I also feel a smooth running FCR is important in A/A combat situations.
Found this out some time ago, I run RTT for MFDs and Helios for the rest of the gauges…
-
Found this out some time ago, I run RTT for MFDs and Helios for the rest of the gauges…
Is it possible to use RTT with Helios in the same device extended with spacedesk? I ask because I share the display with MFD texture and some switches.
-
Is it possible to use RTT with Helios in the same device extended with spacedesk? I ask because I share the display with MFD texture and some switches.
Simple answer is YES
Longer answer: you just have to calculate the correct X Y values for the RTT Client ini where X 0 Y 0 is the upper left corner of your primary display
-
Simple answer is YES
Longer answer: you just have to calculate the correct X Y values for the RTT Client ini where X 0 Y 0 is the upper left corner of your primary display
I read something about RTT in the manuals but I am out of town now and I don’t have access to them. May I ask how would you assign the tablets to RTT? Just using the coordinates?
I will work with it ASA I go back home. -
Yes RTT windows are placed by coordinates calculated from the upper left corner of you primary screen. So if your primary is let’s say 1080p 1920x1080 and your spacedesk is located right of the primary the X pos will start at 1920. If it’s left and your tablet is for example 1024 in width the left corner of your tablet would be at - 1024
Gesendet von meinem SM-G930F mit Tapatalk
-
Yes RTT windows are placed by coordinates calculated from the upper left corner of you primary screen. So if your primary is let’s say 1080p 1920x1080 and your spacedesk is located right of the primary the X pos will start at 1920. If it’s left and your tablet is for example 1024 in width the left corner of your tablet would be at - 1024
Gesendet von meinem SM-G930F mit Tapatalk
Very interesting. It makes the process a lot easier. I managed to download the TEC manual and I was wondering how to use client and server with spacedesk. Now it became clear.
Thanks -
Very interesting. It makes the process a lot easier. I managed to download the TEC manual and I was wondering how to use client and server with spacedesk. Now it became clear.
ThanksOnly client no RTT server involved in such a set up at all
Gesendet von meinem SM-G930F mit Tapatalk
-
Well, tested and confirmed: RTT extraction is smoother on the touchscreen than Helios’
Nothing wrong with Linknets’s profile either, nothing to do with it, this is purely a difference between the two extractions.
Thx! -
Yes RTT windows are placed by coordinates calculated from the upper left corner of you primary screen. So if your primary is let’s say 1080p 1920x1080 and your spacedesk is located right of the primary the X pos will start at 1920. If it’s left and your tablet is for example 1024 in width the left corner of your tablet would be at - 1024
Gesendet von meinem SM-G930F mit Tapatalk
Thanks Oak. I did the way you suggested and it is working like a charm.
(yo)
-
Just updated to Ice’s 4.35-8 Profile, hacked out the gauges onto my lower MFD screens, then grabbed the CPD from the “CDP Only” profile and placed it on my main screen Everything works perfectly except the “Plan” tab data does not change. Data\Map\Fuel tabs are all fine, I am Saving\Loading the DTC, tried Reset in Helios, tried shutting Helios down and restarting, just keeps the same info in Plan tab (incorrect) and does not change. I know it’s likely just me, any ideas?
-
Just updated to Ice’s 4.35-8 Profile, hacked out the gauges onto my lower MFD screens, then grabbed the CPD from the “CDP Only” profile and placed it on my main screen Everything works perfectly except the “Plan” tab data does not change. Data\Map\Fuel tabs are all fine, I am Saving\Loading the DTC, tried Reset in Helios, tried shutting Helios down and restarting, just keeps the same info in Plan tab (incorrect) and does not change. I know it’s likely just me, any ideas?
Did you save the Briefing?
-
-
A new issue (new to me anyway), normally the mouse pointer kind of shadows the BMS yellow 3d mouse cross when you hover over the Helios CPD on my main 3D screen. When I first enter 3D it works fine, but always seems to stop working at some point in the flight. I then have to Alt-Tab to bring the window to the forefront and use the mouse to clik what I need. I have “set g_bEnableExclusiveMouseCapture 0” in config, is there another setting to allow this?
The full config line is:
set g_bEnableExclusiveMouseCapture 0 // (Set at 1 it will) Captures the mouse when in 3D so that you don’t click something on the desktop when running windowed mode -
From version 4.35-3 onwards:
Steerpoints, Course Lines, Pre-Planned Threats, User Designated Targets and User Drawn Lines are now extracted from Callsign.ini and are available to be displayed on the CPD maps.
The option to use a map saved from WDP is now no longer considered necessary and this has been removed.Just curious if anyone - other than me - is having issues with the Course Lines not showing on the CMD Maps with 4.35 U2? I’m using profile version 8 and had it working fine with U1 but since I did a clean install of U2 I can’t get them to appear. I’ve tried all the process steps mentioned throughout this thread (with and without WDP) and they won’t show. Steerpoints and everything else seem to work fine.
-
Did you reinstall to the same location? Remember the ice profile has an ini file that need you to update the location of bms. If that location changed then it can’t find any of the required files it needs to create those map functions
Sent from my iPhone using Tapatalk
-
Did you save the DTC and then reset the profile, it takes a few seconds to generate the images so try the profile reset again.
Then check the PathNames.ini file for the [FALCON_BMS_PATH] which should have been automatically saved.
Then check the Helios\Images\FalconBMS Images 4.35\CPD\ folder and view the MapOverlay_15.png etc. files and check that they have been saved with the current time stamp and that they contain the waypoint lines etc.
Then check your callsign.ini file and check that there actually are saved steerpoints.
-
Did you reinstall to the same location? Remember the ice profile has an ini file that need you to update the location of bms. If that location changed then it can’t find any of the required files it needs to create those map functions
Yes, BMS was reinstalled to same location.
Did you save the DTC and then reset the profile, it takes a few seconds to generate the images so try the profile reset again.
Yes, I’m saving the DTC and resetting the profile.
Then check the PathNames.ini file for the [FALCON_BMS_PATH] which should have been automatically saved.
This appears to be ok as it matches my BMS install location.
Then check the Helios\Images\FalconBMS Images 4.35\CPD\ folder and view the MapOverlay_15.png etc. files and check that they have been saved with the current time stamp and that they contain the waypoint lines etc.
The folder location’s time stamp matches the profile RESET time. However, the map files all have the same created timestamp of March 2021 but a modified stamp that matches the reset. I do see the steerpoints and waypoint circles and numbers. When I open the PNG file, I can’t see lines connecting the numbers but they do appear in the attached file. So, I think this part is ok as well.
Then check your callsign.ini file and check that there actually are saved steerpoints.
I do see location numbers for the steerpoints but I wouldn’t know if the data is right. Looks ok I guess.
Screenshot while flying using same attached map:
If it matters, I’m on Windows 10 21H1 (OS build 19043.1052) and Nvidia driver 471.11
-
That MapOverlay_15.png file looks fine except that it is somewhat corrupted, presumably the original is clear. The connecting lines are very small on a 4096x4096 image so you have to zoom in a lot.
The map files should have their original dates since these never get modified.
The problem seems to be the profile not loading the new images. Try waiting for at least 30 seconds after saving the DTC before pressing reset.
-
Just curious if anyone - other than me - is having issues with the Course Lines not showing on the CMD Maps with 4.35 U2? I’m using profile version 8 and had it working fine with U1 but since I did a clean install of U2 I can’t get them to appear. I’ve tried all the process steps mentioned throughout this thread (with and without WDP) and they won’t show. Steerpoints and everything else seem to work fine.
No issues, Set up mission, Save Mission, Save DTC, Print Briefing, and hit Reset on Helios Panel. Just ran a bunch of Balkans mission online with a buddy, worked flawlessly…