Question regarding performance RTT versus Helios
-
I have a second monitor (no touch) where I am using Helios to display Flight instruments, Fault Panel, FACK and RWR. I use RTT to display MFD’s through tablets with my Thrustmaster MFD’s.
Now I also want to export MFD’s Helios texture to this second monitor big enough to make it easier to see (no FOV zoom anymore).
Question: How will the overall performance be affected in that much “Extraction” environment? I mean Desktop, connection (MP) and BMS performance. I don’t notice differences in performance up to now with 4 devices connected (3 with spacedesk) but I am sure there is some limits. I wonder if I am approaching it.
Thanks :yo:
-
I have a second monitor (no touch) where I am using Helios to display Flight instruments, Fault Panel, FACK and RWR. I use RTT to display MFD’s through tablets with my Thrustmaster MFD’s.
Now I also want to export MFD’s Helios texture to this second monitor big enough to make it easier to see (no FOV zoom anymore).
Question: How will the overall performance be affected in that much “Extraction” environment? I mean Desktop, connection (MP) and BMS performance. I don’t notice differences in performance up to now with 4 devices connected (3 with spacedesk) but I am sure there is some limits. I wonder if I am approaching it.
Thanks :yo:
Depending on your hardware/GPU might not be noticable at all. I have run comparsion test with up to 4 monitors / tablets (as monitors) running the different extraction tools side by side Helios,RTT,Yame,MFDE on a midrange 1660ti and didn’t notice a significant difference if just running one of the or all at a time. As all use the same memory access techique to access the rendered MFD images it not putting more load onto BMS itself.
-
Depending on your hardware/GPU might not be noticable at all. I have run comparsion test with up to 4 monitors / tablets (as monitors) running the different extraction tools side by side Helios,RTT,Yame,MFDE on a midrange 1660ti and didn’t notice a significant difference if just running one of the or all at a time. As all use the same memory access techique to access the rendered MFD images it not putting more load onto BMS itself.
Thanks Oak. This is like a green light. I am going on with the “project monitor”.
cheers :yo:
-
Sasah, just know (for me anyways) Helios’s MFD extraction is not as smooth as RTT, my tests with it had a bit of a stutter/pause… which is why I use Helios for gauges and CPD, RTT for MFD’s…
-
Sasah, just know (for me anyways) Helios’s MFD extraction is not as smooth as RTT, my tests with it had a bit of a stutter/pause… which is why I use Helios for gauges and CPD, RTT for MFD’s…
Yes this is a know limitation of Helios, and the difference between Helios extraction and RTT ones. As oak design stated, depending on your hardware you may have very little to no noticeable difference or you may experience a lag that is uncomfortable to use. Just know that the Helios team is working in a feature that will allow you to enable/config/and launch RTT client all from the Helios profile. This also has the added advantage of having different RTT layouts per profile. So if you have an F-18 BMS profile it can have a different RTT layout than your F-16 BMS profile. This and the ability to manage the configuration and execution of RTT all through Helios will be a very welcomed feature for those that opt to use RTT with Helios.
-
That’s excellent news Wheelchock, one less thing to worry about!
-
Sasah, just know (for me anyways) Helios’s MFD extraction is not as smooth as RTT, my tests with it had a bit of a stutter/pause… which is why I use Helios for gauges and CPD, RTT for MFD’s…
I do the same, thanks Icer :eyebrows:
-
@wheelchock said in Question regarding performance RTT versus Helios:
Sasah, just know (for me anyways) Helios’s MFD extraction is not as smooth as RTT, my tests with it had a bit of a stutter/pause… which is why I use Helios for gauges and CPD, RTT for MFD’s…
Yes this is a know limitation of Helios, and the difference between Helios extraction and RTT ones. As oak design stated, depending on your hardware you may have very little to no noticeable difference or you may experience a lag that is uncomfortable to use. Just know that the Helios team is working in a feature that will allow you to enable/config/and launch RTT client all from the Helios profile. This also has the added advantage of having different RTT layouts per profile. So if you have an F-18 BMS profile it can have a different RTT layout than your F-16 BMS profile. This and the ability to manage the configuration and execution of RTT all through Helios will be a very welcomed feature for those that opt to use RTT with Helios.
Just an FYI as Linknet let us know about the change on the Falcon Lounge. Hopefully I understood correctly; Helios now supports 100fps for the MFDs (vs. 30) so the stuttering/hesitation may be gone on many systems. Today I disabled RTT implementation and removed those MFDs and put the 4.35-11 profile’s MFDs in their place . Result was perfect, every bit as smooth as the RTT extraction and one less software client to run. GREAT JOB guys!!
-
I’m sad to report that the latest version of Helios and Linknet’s v11 profile (well the MFDs thereof :)) without RTT but Helios extracted MFDs still is significantly slower (choppier) then RTT extracted MFDs… at least on my rig.
-
@bvt_9 The version of the profile doesn’t determine the speed of extraction of the MFDs, the extraction rate was improved for Helios version 1.6.5000.0 but as you’ve discovered this is system dependant. The general feedback I’m getting on this is that for systems with faster processors there is little or no difference between Helios and RTT but for older systems there is still a difference. If your system specs are up to date then your Intel Core i7-3770 3.4 GHz might account for the difference between Helios and RTT.