Iceman2

I watched a video about DLSS4 and preset K settings in the Nvidia APP. Doing that fixed everything for me. Smooth sky’s again.

Quick question for the smarter than me people. (All of you) I’m using the pimax 8K in MSFS24su4 AIG models and Sayinterntions TFC injection. My hardware is an Ultra 9 285K and 5090gpu. My performance is amazing (PMDG777, no stutters, good frame rates from Taxi to Landing. However (I know it’s a reported problem currently using SI) on touchdown I get the pop up message saying no more VRAM available and frames go to a slideshow. Sometimes I can wait a minute or two and the system recovers back to good FPS and I’m able to taxi to the gate. Other times the recovery takes longer and I give up and restart. My question relates to VRAM recovery. Would increasing dedicated video memory in the registry be worth it. Or Is a restart the only method?? thanks IM

Thanks for all the feedback. It’s nice to know it’s not just me and my computer. I’m in Australia and it’s been like this all day, so my patience is almost looking like my startup Authenticator progress bar. thx everyone IM

I’m stuck on the start screen. 0% - Waiting For Authentication… I checked the MSFS 2020/24 forums and I see a message from MS saying an Authentication issue has been resolved. Anyone else having this issue or is it just me and my computer. I’ve never had this issue before. thanks IM

Thank you to both of you for your comments. Yes, when using their own AIG software injection I don’t see the missing landing gear. As you say, most likely an Asobo issue where the system is internally load shedding when using different 3rd party traffic injectors. With your input I’m guessing AIG traffic injection system is much more fps friendly and MSFS doesn’t need to load shed. Appreciate your reply.

Can someone be kind enough to explain why and maybe point me to a solution for VR flying. I use the AIG Ai aircraft models for traffic in 2024. If I use the AIG software injection method I have no issues, everything appears perfect. However if I use the Sayintentions traffic injection the landing gear is missing unless I’m up close. I’ve read that this is purely a LOD setting either by the simmer and AI model creator. In SIM my LOD settings are maxed out at 400 and 200. Obviously the problem is not with the models but with how SI uses them. I’ve reached out to SI for advice but was told their system only uses my already installed AI traffic and the problem is with the design of the models. Im confused as to how SI traffic drops the LOD when I’m using the very same models. thx

Same here as of today after I updated the aircraft through the PMDG Control Center with MSFS 2024. Disappointing, VR show stopper. Awaiting a fix. Are we waiting for adobo or pmdg? IM

Thanks to the good folks here I’ve (followed instructions) managed to remove AI default static traffic: by turning the many traffic settings back ON again then OFF while in game in MSFS 2024. This works well when not in VR and removes the static aircraft for VATSIM or Sayintentions. However when I switch to VR all static AC appear again. If I do the above ON/OFF method whilst in VR this won’t turn off the AC. Is it an SU3 beta problem, I don’t remember this problem in previous versions although I’m relatively new to 2024. I’m guessing all static aircraft are streamed so there’s no actual static aircraft files on my drive that can be deleted. Anyone got the same issue with a solution. Not sure if it’s an all VR user problem and on Microsoft’s to fix list or is there only a few VR users with this problem or perhaps it’s only just me. thanks IM

I was happy with the autogen even when it wasn’t perfectly shaped but at least it was clear crisp graphics until I saw the San Francisco Sutro Tower (large tall building) or lack there of. I’ve since found out if I turn photogrammetry on the tower changes shape to the real look and shrinks to the correct size but then all my trees and buildings look bad.

Hi all, New rig 285k and 5090 with the Pimax 8K. Performance for me is excellent and I’m really enjoying the VR experience. However I have a blue circle showing just behind my seat but only when in aircraft that I can’t workout how to remove it. Also I’m getting white flashes far off in the distance along the horizon only when above roughly 20000 feet and when I move my head quickly. Below this altitude I don’t see it. I was thinking it was an overworked GPU but I still get these flashes with all settings turned off or low. I’m using activeSky so maybe that is causing it, I’m yet to try without it. I’ve tried different nvidia drivers without success. One more thing, I do most of my flying around the San Francisco Bay area and noticed the Sutro tower on the hill is tall building not the tower. I have some 3rd party airports like KSFO active but still troubleshooting for a solution as to how the tower got replaced by a tall building. Any help is greatly appreciated. thx IM

Thx, I have already tried the last 3 older drivers without success. However Ive popped a post on the nvidia support forums like you suggested. Also the old card (3090TI) does bring back the special effects. So could be a case of waiting for a compatible driver for the 5090 if they can be bothered with a fix for P3D. Looks like I’ll need to wait impatiently for newer drivers. However the performance boost with the new GPU was nice to see.

Thx, A bit disappointing, but it does seem to point to a GPU or driver issue.

Hi All, I’ve completed a new install on P3dv5 on a completely new rig: 285k and the 5090 latest drivers. Default install no addons. I still have no effects. Anyone else able to comment on their 5090?

Appreciate the response. Yes, I’ve deleted the shaders. thx

Hi all, I upgraded to a 5090 without complaints except I have no special effects such as Contrails and Tire Smoke. I tried older driver options without success. I do use TOGA Envir special effects and have tried an uninstall returning to default effects, also without success. I also tried selecting medium instead of high in the in-game sliders. Anyone got some ideas. Seems strange that a new GPU would cause this. thx IM