oakdown

I'm surprised at this recommendation (otherwise a big fan of Mbucchias work and dedication!) but with my system (3090 ftw3, 13700kf, 64gb ddr5) there is no way I can stop the Fixed foveated rendering (in quad view foveated rendering) for the G2 (non-omnicept), to not stutter in lateral side to side movements. test is simple, boot up your choice of A10C2, f16c, or AV8BA (or likely any others I just didn't test more), and move your head laterally side to side - and watch the console/fire handles etc judder along. amazingly small circular movements with your head while looking down at the flight control doesn't cause the issue. Now I realize you might wonder how often one moves side to side, well even looking left to right or vice versa can cause a similar effect. Uninstall quad view foveated rendering (just disabling toolkit doesn't stop it), and try again - perfectly smooth lateral (side to side) movements looking at the consoles of those aircraft.

Glad to hear it is fixed, that was a strange one for sure

Regarding the toolkit, well i disabled it because I wasn't sure where my settings were at with it, and didn't want any conflicting settings, ie: back to somewhat barebones and build on up. Next step will be to slowly reintroduce some of the toolkit settings to see if it's worth utilizing or not. Regarding motion reprojecting, I find the artifacting to be pretty minimal especially with the f16 maybe a little wavering around the eyebrows, and without it (enabled) my 3 o'clock and 9 o'clock stutter the landscape. I'm pretty happy with where things are at, try it out is all I can suggest.

I run at 90hz

Grodin, I also run a reverb g2, on a 3090, 13700kf, w/64gb ddr5. I do not have your experience at all running dlss, quality preset, dlaa, sharpening at 0.55, pd 1.0 in sim. I disabled the toolkit, but run the openxr tools at 140 percent with motion repro, and prefer frames. I feel I get very little ghosting, and the sim has otherwise never ran better for me. I've mostly been playing the f16. But have done outings in the a10c2 and apache as well.

Ok, this was totally my bad. I've figured out what I was doing wrong and while relatively unrelated to pretense at this point now, and has to do more with my misunderstanding I wanted to post what I found. When I would lay markpoints, I would always wait for the markpoint number on the ded to advance (Ie from 26 to 27)as visual confirmation it took. My problem was in thinking when the DED advanced to 27, it was the markpoint 26 that I had just put in, whereas it was actually markpoint 27 that had just logged. So of course when I went to steerpoint 26 the tgp would look at a location associated with a zone. Pretty silly, but that was my issue.

I've just attempted this again tonight, (getting the f16 to lay markpoints w/ JHMCS) and it finally worked on markpoint 28, after 26 and 27 failed. these are my steps: AG Mode selected HUD with upper left asterisk as sensor of interest TGP pulled up on left MFD, SMS on right JHMCS set full bright Toggle numeric 7 for markpoint on the ICP TMS Up long to get circle in JHMCS pick random spot on the ground I want to land a markpoint press TMS up once to ground stabilize, and then up again to lay the markpoint. visibly check the DED that the markpoint has indeed advanced to "27" from 26 hit the RTN on the ICP Toggle numeric 4 for Steerpoint on the ICP Enter 26 for the steerpoint and press enter attempt everything I can on the TGP (CZ, SP, CZ again, TGT) to get it look at "markpoint 26" instead it will continue to gaze at waypoint 26 which correlates to one of the zones. I'll do this again for markpoint 27 - sometimes it will work, tonight it didn't work until my third go around and finally logged markpoint 28 as one I could look at through the TGP. if anyone can see something I'm doing wrong I'd love to know - having a ton of fun in the mountains taking out the smaller encampments!

Thanks for reply Dzsekeb, I figured it must be finger problems on my end, I'll keep working at it.

Let me preface this by saying I'm not the greatest at the f16 yet. But I'm just curious from other players using the f16, if you are experiencing difficulties laying down markpoints in the markpoint specific range of 26 - 30? I feel like markpoint 26 never takes, sometimes 27 will, and so the whole process has become a bit of a fiddly bit for me to get to work. I feel the underlying issue might be that the waypoints for the different zones go right through 26 to 30 and are pre loaded, and overwriting them with a markpoint is dicey, but then again as I'm fairly new could be just finger problems on my end. This all being said, I'm loving pretense, and some of my best dcs experiences have been playing it!

I'm a reverb g2 v1 owner since being on pre order in canada, before it dropped, on original cable. I honestly never understood all the issues people were having with the cable... I figure most problems must have arose from those that jump about the room beat sabering, or lots of family member headset swapping. Playing seated (sims) and carefully stowing the headset has worked to this point for me. As for you, I would recommend waiting for quest 3, release in the fall, save a couple more pounds until then....

Just wanted to say thanks for pretense! I've been really enjoying it the last couple of nights, and that was without persistance too (which I've set up now). Your dynamic campaign makes the game feel much more alive. Cheers

I get it where the first airfield (Kutaisi) I can contact the ground crews to move in, can visibly see them move in, then in F10 I can announce objective #1 complete, but Senaki is crickets once cleared.... crazy this bug has been around since a year ago? and even with the latest upgrade to this campaign still doesn't work correctly.

Glad you got it going and thanks for testing the issue I've been having. It wouldn't be such a big deal to me (VPN doesnt need to be active when flying either) but its just different behavior then I had in win 10, when I never had to deactivate my VPN. Maybe I'll ask on the forum of "private internet access" might be some Networky types there that know why it's interfering with a local ip/port

Do you have a VPN? I found out recently (still haven't dug deeper) that I have to disable my VPN to get it working.... Symptoms were identical to yours, even tried using other people's versions of export.lua to no benefit.

I figured out my issue with simshaker not getting any input from dcs. It was my VPN. I don't fully understand why that's happening as I've used a VPN and dcs w/ simshaker for years with windows 10. So maybe something different in windows 11 or something changed with the VPN when reinstalled. But I can be playing the game with the dcs debug screen from simshaker open, and as I toggle the VPN off or on, the data (and rumble) coincides with the VPNs state.