Buzz313th

I sent you a DM. Maybe I can be more helpful.

A track file would not show what I am talking about, since the track file only includes the the flight parameters for your computer to render. and a video would be a bad representation of the test. And... I do not have any track files for the F5E and my trial timed out for it... But I can recreate the same scenery ground staccato I am talking about, with my other modules. I would just need to increase the graphical load, then fly over vegas looking at the 3d scenery. It is the same thing I would see in the F5E. If you have VR then I'm sure you can recreate what I'm talking about.. Here are the steps... 1. Pick a high density scenery with lots of 3d buildings 2. Pick a full fidelity module 3. Fly over the scenery at around 5k agl and look out the side of the canopy centering your view on the 3d buildings. 4. slowly roll the aircraft left and right as you're looking at the 3d buildings 5. You should see the terrain move in a high frequency staccato (Not smooth) 6. If you don't see it, then increase graphics quality, scenery density and LOD distance until you do. If maxed out, then increase resolution of HMD and try again. 7. At some point the rendering engine will come to it's knees and you will see what I'm explaining.

Not asking to crowdfund the entire development cost, just to get a commitment to a particular aircraft model, assuming they have the resources and can get the data.

Hypothetical question here. How much money would need to be raised by a crowd funding effort and offered to "Heatblur" to generate interest in committing to finish a fan selected Full Fidelity Module? Cheers

I already disable core #8 and it fixes the longer stutters. Been doing that for months now. The micro stutters I am talking about in the F5E are very short and more of a high frequency staccato that I see when over high density scenery. I can generate this with all my other modules just by turning up graphics setting to max and increasing resolution. My point is that for me, the F5E while in cockpit in VR does it where my other FF modules do not. My trial for the F5E timed out and I made the decision not to purchase, even though I would in the future if the F5E got an update. I'm going to guess that the asset geometry and textures in the F5E cockpit have not been optimized for modern rendering techniques and is just a bit more taxing on the system in VR than the newer modules. Cheers

You could.. But crowdfunding a project like this is not easy and to make it more enticing you would need to offer money back if the project never starts.

Maybe we should just crowd fund the damn Eagle C? And once there is a good size pot of funding, offer it up to a quality 3rd party dev.

Are you on VR? My frame time and metrics are good. It is simply the micro stutters that is the problem.

My wishes as well. Unfortunately for ED, I will probably not be buying a FF Mig29A. I would however buy a FF Eagle C.

First, I would like to know if anyone else is getting the same increased stuttering in the F5E cockpit, in VR, over Vegas, when compared to the modules I mentioned. I don't mind going down a rabbit hole, but only if it will help. I could simply just not purchase the F5E if I am not happy with the way it runs on my system.

I could do all of that, but why?

Wait what? What are you saying?

Using the free trial of the F5E to see if I want to purchase and I notice that there is a noticeable increase in stuttering in the F5E versus my other FF modules, specifically comparing against the A10, F16 and F18 in and around the Vegas Metro area. I know the F5E is an old outdated module, maybe this is contributing to less than comparable performance on my machine, but does anyone know if there are any fixes other than decreasing visual settings? Thanks

You are correct.

Did anything change after yesterday's update with the "Improved Spotting Dots". I'm in VR and I have been using the spotting dots option set to off. But just turned them on to check post update and I am no longer getting large black squares for a2a and a2g objects at distance. Can anyone else confirm?

What VR HMD are you running and at what resolution?

Sounds to me like it's a Vegas thing. When you turn your POV away from the city, does it get better? If so, reduce your visibility range.

How heavy are you?

Umm... Do what you need to do with the throttle, stick and rudder to achieve what I mentioned above. Please don't take this the wrong way, but if you're asking for what G's to pull and what power settings to use for such a fluid situation, I think you need a bit more time in BFM to see past the specifics and on to the realization of the fluid nature of whats happening.

Unload the viper and point at his control zone.. It's a race for you to accelerate faster than him and get the viper behind his 3/9 line. Make him continue using his nose authority to try and keep you infront of him, in turn he stays slow. Pull the viper hard through 400 and then unload and accelerate from 350-450 while you make a mad dash for his control zone. Cycle this sequence at the right times and you will end up offensive. Unload when he is slow and pull hard when he is fast. You have a huge acceleration advantage from 300-500, exploit that. Use the vertical, nose low when you want to accelerate, nose high when you have too much energy. Use the roll rate of the viper. Pirouette in the vertical to keep your lift vector on him. When offensive, fly lag and pull hard for shots. Flying lead will just get you slow.

Great video... After landing flow was missed.. LOL

What was the starting config of the jet?

Thanks for sending it in.. Question.. Am I the only one who can reproduce this consistently?

All good. yeah, at my HMD resolution I gain nothing at 512 or higher. It just puts more load on the render thread when using optical displays. But to keep from having to overcomplicate my shutdown and startup, I just bit the bullet and stay at 512 now.

Thank you.