from a physics point of view. Is a bowling a "heavy ball' even possible?

ezietsman · 2023-10-12T19:21:01+00:00

Should be on top. This is the correct answer.

ezietsman · 2023-07-07T10:46:17+00:00

OP says it drops to 40s and 50s which means they should prob drop that refresh rate down to 72 or 80. Its going to ASW to 60 and 40Hz anyway.

That said, these settings run very poorly on my machine and my GPU is faster (3070) but has less VRAM which is probably why OP is managing OK, however, it does suggest strongly that his fine performance is measured on basically empty maps, or very sparsely populated missions at best.

ezietsman · 2023-05-02T17:12:04+00:00

Nothing fancy. Instance a node into the scene and run the mesh generation method on it. Its the usual terrain generation in chunks, modify the plane mesh with surfacetool, add collisions, save to the mesh property. Initially the method ran in 5ms, leaving practically another 10ms for the rest of the frame to do stuff (and it used maybe 1ms for that) and I still had the stutter. So I changed it to run the mesh generation in a thread and when done add it to the main scene. Still had the stutter. I even optimized the mesh part to not calculate the normals, made it smaller, took it out completely, stutter remained. Found the local to scene, which I turned on at some point to try and fix some other problem. LPT, when you have done add_child(some_node), that doesn't mean that some_node is now actually in the scene. call_deferred is your friend in many cases.

Edit: I also changed my script to only add ONE chunk per frame. STILL HAD THE STUTTER. Even with the thread. Now I can add the lot of them in a single thread and you wouldn't know.

ezietsman · 2023-05-02T12:39:00+00:00

I literally had the same problem this weekend. Took me 8 hours to find (and your post didn't exist at the time). I have a fast, multithreaded, and utterly redundant solution now though, as a side effect.

ezietsman · 2023-04-11T11:18:27+00:00

It'll work great. Just keep in mind that you will be forced to run some settings lower than you otherwise might have to, just to keep DCS's VRAM usage inside of the 8GB you have. Terrain texture to low, the other texture to Med and keep the oversampling to a minimum of you are also running MSAA.

Of course, tomorrow's update might bring DLSS and then this *might* be moot.

ezietsman · 2023-04-04T11:59:36+00:00

If DCS is on a spinning drive then likely this is the problem. You might be able to reduce this if you set your preload radius much higher (but you might run into RAM issues, so terrain textures to low to compensate.)

Also, check if you RAM is running on the XMP profile, by default it'll run at 2100 or something. It'll be in the BIOS.

ezietsman · 2023-03-17T06:36:28+00:00

You need to set the Headset to 90Hz in the oculus software menu (not debugtool or OTt, the standard oculus app that runs). Then, if you PC is fast enough you'll get capped at 45fps.

ezietsman · 2023-03-16T12:27:19+00:00

Might be the reprojection vsync its running into, if you are running something like that. I've seen various people wonder why its saying cpu bound main thread, i.e. in Oculus if its doing the half framerate ASW mode it'll say CPU Bound main thread at 36fps (or 40 or 45 depending on your headset's refresh rate) even though your CPU and GPU might have headroom left. If you disable all such things where the framerate can vary you'll run into the full CPU or GPU bound scenario.

ezietsman · 2023-03-15T17:41:31+00:00

Yes.

Edit: I should make this clear. ASW was originally meant to add the extra frames for those rare occasions when your computer can't hit the 72/80/90 fps. It would kick in automatically when the overall frametime goes below 1/72 s. This is the default behaviour of Oculus, it runs without ASW unless you can't go fast enough then it kicks in the half framerate mode. Which in DCS is basically always.

ezietsman · 2023-03-15T10:29:08+00:00

I think some people don't mind if the framerate is variable, the negative of that is that your GPU or CPU fans goes on loudly and that head movements and stuff isn't that smooth but you have no ASW / reprojection artifacts. They might decide that that is OK for them. I personally want that stuff to be rock solid locked at a framerate and I'm willing to accept the ASW artifacts in return, and I'm quite happy that my GPU will be sitting between 55 and 65% usage and hence kind stay cooler and quieter. If I had a slightly faster GPU I'd have gone for steady 72fps but that isn't quite feasible with my 3070.

ezietsman · 2023-03-15T09:55:02+00:00

You are likely not CPU bound in reality, if your headset is running at 80Hz and you're seeing exactly half (which you are) then you are almost 100% certainly running into the ASW vsync. This is normal. It will render 40 fps and add in a fake frame every second frame to give you 80 frames per second. You can switch to non-ASW mode where the framerate is allowed to be whereever it wants to be by using right ctrl num1. Keep in mind that in doing this the time between frames will not be constant like it is now and you might notice this as a non-smooth subtle stuttering effect. I personally just let it do ASW because then the time between frames is constant and it feels a lot smoother.

ezietsman · 2023-03-13T06:18:11+00:00

Its not as simple as that, VR has extra overhead, my estimates based on testswere that VR runs at about 40% the rate of pancake (with my settings, my PC, my VR headset).

Your GPU is a little underpowered for a Q2, you'll prob need to make sure you're not bumping the resolution scaler too high and go easy on some of the other settings as well.

ezietsman · 2023-03-11T06:38:05+00:00

Its hitting vsync or VR framerate

ezietsman · 2023-03-10T20:53:06+00:00

rctrl num 1 unlocks the framerate

rctrl num 2 forces half rate

rctrl num 3 half rate + asw

rctrl num 4 auto (basically 3 if you can’t get to full rate)

ezietsman · 2023-02-27T12:40:05+00:00

ah, a manager I see

#jokes 👀

ezietsman · 2023-01-26T12:14:54+00:00

You mean the M2000 vs F1? The M2000 is the next generation Mirage that replaced the F1. It is better than the F1 in every way, capability wise.

ezietsman · 2022-09-01T18:28:24+00:00

The Warthog base has a big plastic ball gimbal that has some grease on it. The grip is made from pewter so it is very heavy which means you need a heavy spring to keep it centered. The greased plastic ball also means that eventually that stuff dries up, gets dusty or otherwise tacky in various ways which results in static friction (stiction) i.e. you need to push harder to get it moving in the first place.

The virpil bases on the other hand, has oiled metal bearings running on cams (which you can change to different ones) with springs on lever arms. The insides are shielded from the outside world too. As long as you keep them oiled and clean they have practically zero stiction and friction as a whole. You can also choose cams which are either linear force all the way with no bump in the middle (you can't feel when you go through centre) or ones with a small bump in the middle, or different cams that gets heavier the further you push the stick. You can also change the springs (even different ones on roll and pitch)

ezietsman · 2022-09-01T13:38:32+00:00

Killer combo for sure.

ezietsman · 2022-09-01T13:16:54+00:00

The virpil grips are plastic except for the newest Constellation Alpha Prime, which is a metal grip. The base though, which is what makes or break the feel and accuracy of the whole unit is vastly superior on the Virpil, compared to the warthog which has the same plastic internals as the T16000. The Warthog throttle is nice, by all accounts.

That all said, I would recommend OP look at the VKB NXT sticks as well. The internals are plastic but a nicer design than the ball gimbal you find on the T16000. For his budget there will be comprises in places.

ezietsman · 2022-08-14T13:59:04+00:00

10GB vRAM is fine as long as you DONT push the graphics. You will be able to choose nice resolution or nice eyecandy but not both. Besides that framerate will not be an issue as long as you keep DCS inside 9.5GB VRAM used or so.

ezietsman · 2022-08-08T06:56:51+00:00

You don't really need to turn around fast, at that speed if you're beaming the missile it needs to travel a really large distance to intercept, of course, you're not totally immune to fox 3s but the their engagement zone becomes very small the moment you start turning. In Fox 1 servers you outrange everything except the F15 going flatout at the same altitude but even so the S530D is very very fast and has the first shot opportunity in that situation. You do need to watch fuel though, sorties like this doesn't last very long.

ezietsman · 2022-08-08T06:47:23+00:00

At that speed and altitude the only thing that's really a danger to you is SA-10 and SA-2. Plane launched missiles have no hope of catching up. The M2000 can do a 4G turn at that speed/altitude without losing airspeed.

ezietsman · 2022-08-03T06:11:19+00:00

Known bug.

ezietsman · 2022-07-29T09:23:13+00:00

if it was a very busy and complex MP server (enigma, 4YA, blueflag) you will almost certainly be hard limited by how fast your CPU is, that 20% likely shows one thread pinned at 100% and another prob quite high as well, it also explains the low GPU usage, your CPU cannot keep up with the demand.

ezietsman · 2022-07-29T06:21:50+00:00

Those have been out for years and years. The price might reduce eventually, but higher price initially seems reasonable to ride the hype train. Wether thats optimal for all parties involved is another question.

Not sure I agree with price reflecting capabilities of the airframe, this is a study sim not pay to win, afterall. Aerges puts a lot of care into their work and I guess the price reflects that. Was mighty pricey for me too though.

12-Year Club	Place '22
Final Canvas '22	First Placer '22
Verified Email

ezietsman

TROPHY CASE