divinee

F-16 with harms and HTS is just so overkill with AI SAM's. You can loft HARM's from about ~60nm, they will go to space and dive from there 1000kn+. Even SA-15 and SA-10 have a hard time with HARMs. Kinematicly F-16 is propably the best for SEAD and combined with HTS+HARM i think there's just no comparison. Edit: We really need skynet etc or real IADS system so AI SAM's wont make suicides Then it's more about tactics etc than just aircraft and it's capabilities.

I can confirm this. Waypoint 25 cannot be used as Bullseye. If steerpoint 25 is selected for bullseye, indications will be for the missions bullseye, not waypoint 25.

Also had the same. All sensors were jammed to that same position where the emitter was seen in HAD. Even jdams VIS cue on HUD went there immediately. CZ didn’t work. I was able to put litening to SP but that was all. Sadly i wasn’t able to get track.

I’m not assuming anything. Just pointed out something. Like i said, everyone can do whatever they want and what suits them. This conversation seem to move to personal stuff so i’m not gonna continue it anymore.

Yeah, that's always possible. I didn't mention that because usually people know not to change lighting radically when using inside-out-tracking at least when they are flying (hopefully)

The issue is that you have to do that When the environment data is ok, you will not drop to 3DOF in the middle of running DCS.

Just explained that there might be some faults in your method knowing how the inside out tracking works. But go ahead and do what suits you. No one forces you to do anything

G2 is not using SteamVR reprojection. SteamVR just relays the settings for WMR. WMRFSVR and SteamVR settings really use WMR's own reprojection. https://docs.microsoft.com/en-us/windows/mixed-reality/enthusiast-guide/using-steamvr-with-windows-mixed-reality

When glasses drop to 3DOF and lighting etc is ok (good, uniform lighting and no blank white walls around) it usually means there is faults in the environment data. It is possible to still get the tracking work again like you have described but the faults are still there. The environment changes a little bit all the time (you move stuff on the table and so on..) and it is quite usefull to clear that data from time to time. With a good environment data with G2 you don't even have to turn your head to calibrate the glasses to the environment. Clearing and teaching new environment takes less than 1 minute if you are using only seated position and requires about 10 mouse clicks. Then you don't have to hassle with wmr on-off-on, stemvr on-off-on, turn your head and so on. With boundaries it takes few more minutes but you don't have to do that every day.

The glasses still can lose the orientation for various reasons and still all you have to do is to clear environment data from windows vr-settings and teach those again (boundaries or seating position).. Reinstalling software is a little bit overkill for tracking problems, just for the clarification if someone else is having 3dof problems.

It's not a bug, you are in a 3dof mode. Mostly happens when you change stuff in the room. Please clear the environment data and teach the room or sitting position again.

G1 has different percentage numbers in SteamVR. 100% means the native, about 2160x2160 per eye resolution. 6900xt should be more than sufficient to run G1 with 100%. (By the way, i’m able to run G2 with 75% SS, about 2700x2700 resolution with my 2080S and i have quite stable 45+ fps everywhere else execpt marianas.)

https://nvidia.custhelp.com/app/answers/detail/a_id/5196 Official nvidia link for the hotfix

Just to inform, i installed nvidia's 466.55 hotfix drivers and i haven't got any crashes with wmr for steamvr beta. Have anyone else tried that? edit: running windows 21H1 and steamvr beta

I'm using english version and i've been having those crashes occasionally. After installing latest hotfix drivers from nvidia(466.55), i got rid of that crashing at least temporarily. I haven't been able to reproduce that crash since yet but time will tell. Also at the same time i got rid off the wmr for steamvr beta crashing.

It depends on how long it will take to implement that DTC. We haven't heard any news from it for quite a long time so i wouldn't expect it too soon. But yeah, there are more critical things in F-16 which should be implemented first but markpoints would just ease up some things quite a lot.

Why it’s not possible to limit the number of the navpoints what we have now to 25 and then use 26-30 as markpoints almost like hornet does? All that is needed is changing of the icons in hsd and not using connecting lines. The rest of the points can be implemented when possible (like with dtc). Even that would be more usable and closer to real thing that what we have now? edit: points 31-127 could be left as editable in mission editor so those could be used to limit areas etc. More work but still less than overhauling whole waypoint system and implementing data cartridge

Any info about this? Is this still considered by ED?

Does it have something to do with 2000-5?

You have quite a lot of more VRAM than previous posters and ~most of the VR users (11gb vs 8gb). To easily replicate these kind of situation you need to crank up the SS% or texture settings a lot so your vram usage increases to same levels..

Yeah, i’ve been in sim scene since -99-00 so nothing new to me Just wanted to point out that even ED is now starting to mention april so people better not to get dissapointed if the patch is not coming in march.

And you have 24gb of vram? That kind of solves/fixes most of this problem