threexgreen

Oh, I didn't think you actually achieved the locked rate of 63/32-ish in that screenshot. That's what I'd love an airport to look like. I'm gonna have to try that with the balancer, stutters or not. Is the display of AI aircraft GPU or CPU-bound?

What FPS did you get in that scenario? Also, I assume that's with frame generation. Do you know what FPS you would get without FG?

Is that the override resolution option in OpenXR's in-game overlay or the scale slider in the app itself? Thanks.

I haven't tried it with the latest version but a while back with a previous version it worked very well with the PMDG 737.

I don't see why data is an issue. Weather data is already being read and displayed on Asobo's proprietary radar. AFAIK, the issue for developers is there is no tilt function in Asobo's radar, making it unrealistic. If Asobo weren't so reluctant to add a tilt function for whatever reason and provide a proper radar, developers could just use that (as some are already doing) without having to build one on their own, and thus without the need to expose data. In short: If Asobo added a tilt function we would have a realistic radar for all third parties to use and no one would need data.

Did you notice any loss/lack of traffic due to traffic injection being paused?

What do you use to oversample? Do you use DLSS or TAA?

Anyone dare to make a guess as to performance in MSFS with the Super model at 3,840 × 3,840 plus the wider FOV?

Thanks, that would be very appreciated. Although I think it's clear it's an issue on my end. I'd still be interested to see if you see any sort of unusual performance drop from descent to the end of the flight though.

I've said repeatedly I'm going to do that. Other than that I've tried several times to explain what my issue is and why I suspect it may go deeper than the balancer, regardless of using it or not, in case I wasn't explaining it well enough. But it doesn't seem to garner a lot of interest in the first place and is instead dismissed as me complaining about how it works and refusing to heed advice. The point of this thread was to find out if others have the same issue. I think we have an answer on that, so I'm going to file a ticket as soon as I have the time.

Please don't get me wrong - I didn't say you were lazy or that the balancer is a bug fix. I even said earlier I'm going to enable it. I'm not ignoring the recommendation. I'm just not sure if I'm supposed to enable it for a log file if it completely halts CPU calculation and therefore eradicates the stutter issue I'm facing or if it's better to leave it off for that log file so it can record data on the issue. It seems this still isn't fully clear, so I'll try again. I'm not talking about normal, sporadic stutters or a small FPS loss as a result of more calculations - which would be expected. I'm talking about severe, out of the ordinary stutters that almost lock up my CPU. So I think that regardless of the balancer feature, there is something amiss. We're also still talking about a beta version, so I'm not sure why the idea I'm having an issue is seems to be so elusive. And for the record, I'm not complaining, I'm trying to get help. I think we're having a communication issue is here.

I appreciate the input. I have a 7950X3D too, which provided a juicy boost in performance over my previous CPU. I "only" have a 3090 card though, so I can't utilize frame generation and even if I could, it doesn't work in VR. I'm sure that running at double the "normal" FPS is a fine experience, but I also think that 40 cards are still not mainstream even if it seems many flight simmers have upgraded to one. FG and no FG are very different use cases. That said, I know from my very own experience it's possible to have a stutter-free experience with FSHud with decent frames, even if I have no way of doubling the FPS. Since the last update that experience is gone for some reason however, which is my problem.

I'm having an issue since the separation update where I'm experiencing severe stutters. I haven't used the balancer before because I'm using traffic settings that keep FPS within an accepted margin, so there was just no need to use this feature before. I understand that using the balancer now that I experience severe stutters can alleviate the issue. I don't know how the technical log works. So I was wondering if this file records any information as to whether there are performance issues, and why. If the balance feature however were to halt CPU calculations and, as a result, the stutters didn't occur, I was asking if there would still be information on the stutter issue in that file, or if it were better not to use the balancer to ensure the stutters occur so they can be recorded in the technical log to be able to better analyze the issue. Essentially, if I took away the problem, there would be no problem to record, right? The reasons why I think there is a deeper problem that I'm running into and this is not just me using unreasonable settings are: A) I use traffic settings 20/20, which depict only little traffic to account for FPS. B) These settings worked fine from when I first used FSHud until the separation update, with no performance issues and no stutters. C) I haven't changed anything in FSHud, MSFS, or my system that might explain a sudden performance loss. D) The stutters occur only at a specific stage of flight. In other words, before arrival I use the same traffic settings but there are no stutters whatsoever. E) The stutters are more than your usual stutters. They are so severe that the picture in VR keeps lagging and freezing every few seconds. F) My CPU is generally powerful enough to handle any decent load. It is normally able to handle traffic at 20/20 without any stutters, as it did before. I don't generally oppose using the balancer, but I don't think it should be a solution to the problem in this case because I see no reason why my system wouldn't be able to handle traffic at 20/20 without the balancer all of a sudden - as it always did before. This is a summary of what I said in the thread. I hope this makes it clearer. I don't know how else to explain what I'm trying to convey.

@FSHud Life got in the way and I'm going to have to try doing a flight in the next few days. If it's any help I can file a ticket now, though I'm not sure if it wouldn't be better to file it with the associated log right after a flight of experiencing stutters in case the log contains any information on that. I was at the gate with FSHud already running before I had to abandon the flight, so I'm not sure if that overwrites any information from the last flight.

There is no problem, I was just wondering if the balancer were to stop CPU calculations and I got no stutters, if a performance issue would still be apparent in the file or if it would be 'hidden'. I managed to rearrange some things and am going to do a flight now without the balancer in case that's better for logging the stutter issue.