Ice’s Falcon BMS Profile Updated for BMS 4.37
-
Great work and thanks for the support!
A couple of rookie questions that I can’t find an easy answer for:
1. Is there a button somewhere in the panels for the TrackIR reset (F12) hotkey?
I did manage to change the “Hot Start” hotkey to TrackIR reset, but I had to edit the keyfile as well because the F12 callback was not showing up. Basically I copied this line SimDoNothing -1 0 0xB7 0 0 0 -0 “UI: Screenshot (See also section 6.06)” (line 23 in Note++ in Ice’s Helios Keyfile) and pasted it over this line RecenterTrackIR -1 0 0XFFFFFFFF 0 0 0 1 “SIM: TrackIR Recenter (additional)” in Section 6.06 (line # 1000). Otherwise you will not see “Recenter TrackIR” when you search in the Helios Profile Editor.
Clear as mud, I hope. :thumb:
Cheers,
Jolly -
I did manage to change the “Hot Start” hotkey to TrackIR reset, but I had to edit the keyfile as well because the F12 callback was not showing up. Basically I copied this line SimDoNothing -1 0 0xB7 0 0 0 -0 “UI: Screenshot (See also section 6.06)” (line 23 in Note++ in Ice’s Helios Keyfile) and pasted it over this line RecenterTrackIR -1 0 0XFFFFFFFF 0 0 0 1 “SIM: TrackIR Recenter (additional)” in Section 6.06 (line # 1000). Otherwise you will not see “Recenter TrackIR” when you search in the Helios Profile Editor.
Clear as mud, I hope. :thumb:
Cheers,
JollyDoes that mean that you’ve used the “Hot Start” button for TrackIR Reset? If so have you lost the original function on this button? Wouldn’t it have been easier to just create a new button for TrackIR Reset?
-
Does that mean that you’ve used the “Hot Start” button for TrackIR Reset? If so have you lost the original function on this button? Wouldn’t it have been easier to just create a new button for TrackIR Reset?
Exactly what I would have supposed as well. As simple as dragging a new button into the profile. Next I would not set it on a subpanel that requires an additional touch. Just place it on the main panel and maybe a second one on the enlarged main panel
I personally fly exlusevly Multiplayer and about 50% of the events require Ramp Start 50% Taxiway. And sometimes you have to reconnect in Air so all 3 button presets are really essential
Gesendet von meinem SM-G930F mit Tapatalk
-
Does that mean that you’ve used the “Hot Start” button for TrackIR Reset? If so have you lost the original function on this button? Wouldn’t it have been easier to just create a new button for TrackIR Reset?
Exactly what I would have supposed as well. As simple as dragging a new button into the profile. Next I would not set it on a subpanel that requires an additional touch. Just place it on the main panel and maybe a second one on the enlarged main panel
I personally fly exlusevly Multiplayer and about 50% of the events require Ramp Start 50% Taxiway. And sometimes you have to reconnect in Air so all 3 button presets are really essential
Gesendet von meinem SM-G930F mit Tapatalk
I fly MP too and 99.9% of the time I just click Fly/Taxi. The other 0.1% of the time I fumble my way through a ramp start so Ramp or Hot starts are just superfluous. So I changed them to suit my technique, which includes centering my sticks & track IR before flying. :thumb:
-
I fly MP too and 99.9% of the time I just click Fly/Taxi. The other 0.1% of the time I fumble my way through a ramp start so Ramp or Hot starts are just superfluous. So I changed them to suit my technique, which includes centering my sticks & track IR before flying. :thumb:
I still think that it would have been better to leave the Hot Start, Air Start and Ramp Start buttons in place should you need them even very occasionally and enlarge the panel and add a row of additional buttons for TrackIR, or better still use oakdesign’s suggestion and add them to the main panel.
-
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.