Powayjoe

Hi Pete I contacted LM again regarding the Radar Contact window not showing up in VR and they responded saying the only interactive windows that will display in VR are Scaleform windows. Windows such as their ATC and the add-on SODE windows for example are Scaleform not SimConnect. I know this might be way too much to ask but is it possible to provide the RC window in a scaleform format so all of us VR flyers can make use of it. If not could you direct me to where I might be able to get assistance in doing so? Thanks again for all you have done for our hobby! Joe

Sorry for the double post. I will inform LM that it is a simply SimConnect Message Window which they say should show up in VR. I was worried that since FSUIPC remembers the size and position of the RC window and opens it at the next use according, which does work, that maybe that was confusing P3D and therefore wasn't being recognized. I have read the RC and FSUIPC manuals and have everything checked as should be and it all works fine. Thanks again for everything! Joe

Pete, First let me tell you how grateful I am for all you have done for our wonderful hobby. I posted a topic on this forum regarding my issue with displaying the Radar Contact window in native VR. I also posted on the LM forum and this is the reply I received: Hello,Is the Radar Contact you are using something you have developed, or possibly a 3rd party add-on?Scaleform windows should show in VR. If the message window you're referring to created as a Scaleform window, you should be able to make it appear in VR. Here's some more information on Scaleform panels:https://www.prepar3d.com/SDKv4/sdk/pane ... orial.htmlRegards,Kayla I was wondering if the issue is because the interface window is actually being created and/or manipulated by FSUIPC. I run the latest paid version and it works beautifully in 2D as I stated in the other post. Any insight would be gravely appreciated. Joe

I recently installed the free released version of Radar Contact and it works beautifully. I can utilize all the features and interact with it just fine. However when I switch to a Native VR in P3Dv4 the message window will not appear. I have the latest paid for version of FSUIPC installed and have worked with it extensively. I have read that in the past there was an enhanced window that was developed and could be used with FSUIPC but no longer works and I believe was abandoned. I also see that FSUIPC will remember location and size of the default message window. I posted on the LM forum and they said Simconnect Message Windows should appear. My question is, is there something FSUIPC is doing to the message window that might make it not appear in native VR? Any help would be appreciated, thanks in advance. Joe PS this is a reply I received from the LM development team on their forum. I also found another post reply of yours stating RC4 window doesn’t use Simconnect could this be the issue because it’s not a Simconnect window and hence will not display? If so any suggestions on how to see the RC4 messages in VR? Hello,Is the Radar Contact you are using something you have developed, or possibly a 3rd party add-on?Scaleform windows should show in VR. If the message window you're referring to created as a Scaleform window, you should be able to make it appear in VR. Here's some more information on Scaleform panels:https://www.prepar3d.com/SDKv4/sdk/pane ... orial.htmlRegards,Kayla

Hi Pete I had one more clarifying question so to be sure I understand something. When the Target Frame Rate variable is set to 0 (zero) in the .ini file then the limiter will reduce the aircraft to the number set in the Traffic Limit variable right at startup and continuously thereafter whenever the number of aircraft exceed the Traffic Limit setting correct? Or said another way setting Target Frame Rate .ini variable to zero disables the function as if it weren't there. I assume this setting would be the best approach to limit VAS issues? Thanks in advance Joe

Pete Thanks for fixing the "missing" entries in the FSUIPC.ini file regarding Aircraft Limiters with version 4.964. I assume they are working but I manually added them yesterday before the release so when I installed the latest release over the previous as I always do they didn't change and the values I had set stayed the same, so again I can't be sure they would have shown up since I had already manually added them. On another note can you tell me if there is a negative impact if I set the P3D AI slider too high when using MT6 since if I use the Frame Rate Limiter option it would remedy the higher aircraft count automatically. I traditionally have been setting my slider around 20% and the number of aircraft in your app to 100. So if I were to theoretically increase the slider to 100% and all of the FSUIPC limiter settings stay the same wouldn't the aircraft be the same? Or would the number of deletion responses increase so that I would see momentary stutters or performance hits and therefore I should strive for an optimum slider % for AI in P3D combined with the relevant settings in FSUIPC? I am just trying to best understand how to maintain realism while minimizing frame rate hits. I run a 30 Hz 4K TV at 30 FPS with Vsync and TB and my system runs well as long as I don't drop below 30 FPS for too long and obviously AI can do that. I try to achieve the same results as you do with airports being more loaded with some activity happening there and less in the skies around me. Thanks for your great value added to our hobby and also for your timely efforts! Joe

Hi Pete I have an issue I can't figure out. I have installed the latest registered version of FSUIPC 4.963 on my flight sim PC and WideFS on my client PC and everything works as it should. However when I went to use the AI Limiter my .ini file only has 3 options to set not the full 5. I have: NEARPREFERENCES TARGETFRAMERATE and TRAFFICLIMIT I set these 3 and even loaded a flight plan but I can't seem to figure out why I don't have GROUNDPREFERENCE and AIRPORTPREFERENCE options available in my .ini file? In a previous version I had and was able was able to set GROUNDPREFERENCE before you added the recent additional settings. Please advise Joe