grifnizzle

ahh, ok, I thought for a second it was judging me for crappy formation flying, or a less than impressive break on the second pass, or not waving to the crowd as I passed by. I mean, all would have been valid criticisms lol

Question: what is required to get 100 in the photo op? I got an 80 and I'm just curious what I messed up on.

I updated my thread, plugging tail fuze gave 100% detonation rate. Still curious if that's "accurate" or not but for now good enough for me

So finally had a chance to redo my test with tail fuze plugged, and SOB if it doesn't work. 100% boom rate. Question still stands why equipping tail fuze causes such inconsistency, maybe that's the way its 'supposed' to work? Be nice to get some clarification on that, but for now I'll accept DON'T USE BOTH NOSE AND TAIL FUZE as the solution. Updated track for proof spittybombs broken questionmark TAIL PLUGGED.trk

So does tail fuze HAVE to be plugged? I haven't had a chance to retest yet but I've been having problems with Spit bombs as well, not AI, player (me) released.

As stated in original post I started at 10k, track file will show I performed releases at various altitudes in active pause, all were inconsistent in detonation

ok then not relevant to my example, both nose and tail fuze at default, which I'll have to check again in the ME but I do believe was 0 seconds, with 6 rotations for the arming vanes

So tail fuze HAS to be plugged? That's never been a thing before, why would it matter now? That said I'll give it a whirl, see if it makes a difference. Thanks for the heads up.

I noticed a very high failure rate while bombing in the Spitfire. I made a quick mission with Spit starting out at 10k ft a few miles north of Kobuleti dropping in the large open field from various positions while in active pause to make sure the release parameters were the same for multiple releases (unlimited weapons was on). Over at 50% failure rate of the weapons to detonate. Track included spittybombs broken questionmark.trk

Tried the desktop shortcut method (won't launch/crashes right after chief logo pops up), and adding argument to properties in steam itself (half and half won't launch/launches normally with no difference/steam overlay). Anyone else use steam (I know, I know! I have my reasons) and rockin' an Aero? Niche within a niche within a niche, I get it, but fingers crossed cause I'm flummoxed

Posted in the Aero set up thread but figured I'd ask here too in case anyone had any tips/ideas: Been fiddling with my new Aero this week and having issues really dialing in the cross eye tool. Swapping top/bottom for both eyes improved the image 95%, but getting that last bit dialed in where there's no more 'double cursors' in the cockpit anywhere is proving elusive. Everytime I try to adjust the slides beyond the 'swapped top/bottom' values I just end up making it worse and having to start all over again. Any tips/tricks for a smoothbrain?

So when I hit start in steam and it gives the 3 options ("Play DCS", "Launch in SteamVR Mode", "Launch in Oculus VR Mode"), selecting SteamVR mode isn't sufficient?

Been trying to tweak my new Aero for the past week and I'm still confused on a few things. First of all, I'm running the game via steam, not stand alone. Do I still have to include the -- force_steamVR command? Isn't that redundant if I'm launching from Steam? For the heck of it I tried making the desktop shortcut with the command line add anyway it DCS just wouldn't launch. Also having issues really dialing in the cross eye tool. Swapping top/bottom for both eyes improved the image 95%, but getting that last bit dialed in where there's no more 'double cursors' in the cockpit anywhere is proving elusive. Everytime I try to adjust the slides beyond the 'swapped top/bottom' values I just end up making it worse and having to start all over again. Any tips/tricks for a smoothbrain?

Does the OpenXR mod work with the Index? Or is it only a WMR thing?

so to make sure I got this right, under IFEO select new > Key (DCS.EXE), then under that new > key again (PerfOptions), then under THAT new > dword (32bit) and "CpuPriorityClass"=dword:00000003 that bout right?