maxTRX

I'm not sure which thread should I stick my happy remark into, this one is as good as any... I fired up the sim after today's fix, did not 'force' the .exe to load OVR but I do have OVR installed (no toolkit, just OVR tools from MS) The SVR box showed up though. I checked to confirm it was using OVR runtime. I also looked MS OVR tools and it showed it installed. Whatever the hell I'm running on, it KICKS BUTT! Smooth and fast. I saw couple of micro stutters on the first run, after cleaning up FXO and meta folders. The second run and after, no stutter whatsoever (about 1 hr hop) So... for now I'm happy.

That and for closed beta testing and comm (on all channels): I'm the blue face.

Nope

Since the gun director reticle is definitely tied to the foresight in the recent rendition of Hornet's gun modelling... how can I take a quick shot from an 'out of plane' position on a maneuvering 'ace' bandit when my reticle is showing me an insane and unachievable solution... unless I decide to spend 10 or 15 min. following the bandit's wild and 'perfectly' timed shenanigans. Is there a way to switch to a non-director mode using a funnel or something similar or simply get rid this 'foresight'? If I reject the GACQ lock, the funnel shows up momentarily, then the GACQ or any other gun ACM mode locks the bandit again quickly and... back to square 1. This is just silly.

Well... I always thought my communication skills were lacking. C'mon ED I was a happy camper in SVR with no 'composites', tool kits, replacement dll's, reshades, whatever. I have a decent rig and the only adjustment I made was 200% resolution multiplier for DCS. No AA of any kind. Aniso x16 in DCS. Ran very smooth in SP (I don't do MP currently) FPS 50 ~ 80, well 90 looking at the sky hehe. When I fired up DCS after today's update, I noticed a popup message on my WMR window, telling me that without OXR 'some' games might not play correctly... hmm. There was a 'Fix it' button next to it so... I fixed it, lol. Basically, the SVR box disappeared and I wasn't able to adjust anything. The sim started though and looked good. Smooth and fast. I was intrigued tho' and decided to force it back to SVR in the developer options. After the restart... looked good for a few seconds then micro stutters started. Every 10 secs or so. I can run modest FPS but the stutters drive me nuts. Went back to OVR and decided to stay there for now. No stutters, FPS the same as before. I'm still running w/o any AA. Looks good but yea... slight shimmers. I'm not going to d/l any extra stuff for now. I like to fly, not stare at FT graphs and spreadsheets. I admire people that have patience for all this. I'm just not one of them.

You can say that again . Hornets, Rhinos and... all right!, Eagles and Mudhens. I wouldn't snicker at Raptors either. I think I have it backwards but that's OK.

I didn't notice any obvious difference using Reverb G2. (in SVR)

Since you bumped this thread up, I have to update my loosely related post (right above yours). CCIP @ higher elevations after JDAM power up seem to be fixed.

Not a damn thing, lol, just one of those spontaneous OT exchanges, that's all. It's done

I meant 'Application Controlled' not OFF for AF in NCP. Speaking of AF, when set to x2 in NCP while keeping AF in DCS set to x16, I noticed considerably less 'barber pole' type of shimmer when looking at rooftops from certain lighting angles. I always thought AF in FCP had no effect on in-game AF setting, regardless of 'enhance' or 'override' setting for AA. This was just a spontaneous observation, still have to compare these 2 settings from exactly the same distances and lighting angles before I plaster some happy faces here. BTW, the AA gamma correction turned off didn't seem to change the 'sparkling' shimmer in my test, at least at first glance. I'll play with it some more later. Anyways... since we're mainly discussing OpenXR in this thread, I've decided to experiment with it a bit when I get a chance, just for the heck of it.

I'll be damned... I found one at the bottom of my bookshelf drawer. After 40 years

When I recently got my 13900k with 64gb of DDR5 and finally went back to win11 (with latest updates), someone suggested to give it a shot and leave the bios alone and setup the power management in windows and forget OC'ing... let the damn thing manage clocks and voltages on its own. Yea right... It was worth a try though. In bios, I only did couple of minor changes, disabled HT and reluctantly left all the C-states enabled (including C7... whatever the heck that does). I left the virtualization enabled. In windows, I selected balanced power scheme and modified it a bit, stuff like USB, WIFI, etc. For CPU, I set the limits between 30 and 100% Also, just to see if it makes any difference, I left the memory integrity feature enabled in windows security. It didn't make any difference in performance on my rig. (the recommendation for gaming is to disable it) It's humming along! When I run DCS, the clock is at 5.5 GHz without a hiccup (it starts at 5.8 then for some reason settles at 5.5) The temps are around 50, 55'C. I might try to OC later on. It should be easy to bring it up to 6.2 or so. Pcores, Ecores... , affinities and so on... I'm not going to mess with that. This CPU is a totally different game.

Trilinear and AF were always off but the gamma correction was on, will try with it turned off. So far I've been very successful letting my brain tune the shimmers out . As far as my DCS options go, I've probably tried every combination possible but since I'd been playing SP for the last couple of years, I always end up maxing everything out. Well... not everything. Heat blur, Sec shadows, MSAA, DoF, Motion blur, all SS's are off. I keep the shadows on high though. In cockpit they add up a lot of 'feel', although when looking at external models, in form flying for instance, they look like crap. I stubbornly refuse to compromise on Vis range, always keep it on Extreme. The clouds, I stepped down one notch to high. All sliders to the right, Gamma on 2.0. I like 2.2 or 2.3 at night, during midday hrs I prefer 1.7. I'm still trying to decide on OpenXR since on my current rig, even in SVR I'm getting 90 FPS at high alt and between 55 and 75 when flying over Beirut at low altitude... kinda works for me for now.

First, I don't know what's wrong with me... I'm still on Steam VR. For me, DCS (maxed out for single player) in G2 had only 2 acceptable options: 1. Aniso x16 (in DCS setup), no AA, 200% res. (4472x4364) in SVR. Mid to low FPS but smooth and... shimmers. I know, in MP I'd probably have to stay on the ramp and watch the slide show as a spectator. #2. Aniso x16 in DCS, 100% res. in SVR, AA x 8 in NCP. No super sampling. Looks sharp but shimmering is still there. Yes, AA set in Nvidia panel always worked for me though I'm not sure how it combines with other types of enhancements. Aniso set in NCP never seemed to have any effect on DCS on my rig. I never had a chance to check how SGSS would work in DCS. I'd have to download NV Inspector to find out, I guess. As far as MSAA... I love it on a pancake screen but I hate it in G2. It makes everything look too 'soft' or even blurry, in spite of MSAA mask set to 1, in DCS setup. Currently, I'm on a new rig but the above setup still holds true... everything runs a lot faster though . Still, I'm looking forward to a new graphics engine. Hurry up ED!

Track from the first part of the vid. I switched from the NAV mode to GACQ with the weapons select switch. I this case the 'foresight' is not visible but the pipper is definitely following it. Gun tracking_Offensive1.trk

The reticle seems to follow the FORESIGHT cues, not the predicted rounds impact at target's range based on ownship position at the time of fire. It's fine when the shooter is in the same plane of motion as the target but when the bandit starts maneuvering wildly, the FORESIGHT starts spinning left and right and since the reticle follows it, it spins and jumps all over the place. On top of that, when you factor in exaggerated nose wobble after loaded rolls (very little dampening), the steady aim becomes very difficult. Also, when selecting guns directly from NAV mode, the FORESIGHT is not visible but the reticle dances and jumps like it's still following it. When going to guns after an STT lock, the FORESIGHT is visible. A short footage showing these 2 situations (will provide the track if really necessary):

Yea, it looks like the pipper is following the 'foresight' cues not the ballistics based on your own jet attitude. The range and other factors seem to be calculated correctly so when close enough for a shot, the pipper creeps into correct position, when in the same plane of motion. You can see this when you have the target locked and he starts jinking while you maintain steady path. The pipper is reacting to his maneuvering and is following the 'foresight' indications. Another thing... when you lock the bandit by simply switching to guns, without any previous A/A mode selected (or weapon), you don't get the foresight cues but... the pipper is following these cues anyway ;/. This can be pretty confusing. I think we need to post another detailed report.

I find the reticle quite accurate and being a gunzo freak I put it to use very frequently, although currently in SP only. I'm not saying that there is no problem, perhaps MP adds up more chances of things getting screwed up, I don't know. You might find it a bit OT but for me HMD integration with HUD presents more of a challenge in VR. I always shut it off when HMD symbology gets close to the HUD. Well, I don't want to take this even more OT... One thing to remember when taking snapshots from extremely close distance, other then trying not to wear some of the bandit's parts when doing scissors for instance, use HUD's gun cross and 'drag' the rounds as needed.

Finally... I managed to record a track that played correctly by staging the fight over a flat part of the desert area, away from everything. Well, there's no guarantee the track will play correctly on any other rig. Just in case it doesn't, I'm also posting an unlisted vid recorded from this track. The issue usually shows up when the target closure rate goes from positive to negative or vice versa and the target's crossing angle is high. In this track it starts happening after the second turn in this 2circle fight. ACM break lock problem 1.trk https://youtu.be/cubQiG50sw0

Trust me, I'd rather provide a track but 99.9% of track recording of this type of maneuvers will get out of whack after 1 or 2 turns. The mission was as simple as I could make it: SP, just me and 1 bandit jet 30 nm apart, head on. Guns only load, 80% gas. No wind, no clouds. Well, I could've picked a better area on the map, like featureless desert or water. I'll give it another shot. As far as MP goes, perhaps someone else could try, on some 'abandoned' server with couple of jets only?

Even if ACM lock was very easy to break, the locked tgt symbology should disappear from the HUD and HMD immediately, regardless of what the radar is doing to maintain the lock. Once re-acquired, it should show again. The way it works currently... I's rather turn the radar off and use the funnel ;/

Is this what the devs were referring to? To me this looks more like HACQ getting stuck then 'lagging' and it's still there:

I could swear it did have that authority a (long) while back but... it's all hazy now in my head. All that 'sitting in front of the screen' is not helping either

Yea I know about the paddle, who doesn't these days . If that's what EM charts say them all I can do is... post another tribute to my favorite powerhouse:

Is edmuss the only one that got the fix... anyone else? I didn't bother updating just for the 'mosquito' fix ;/