unlikely_spider

And so shall the battlefield be covered in a thousand mangled Chinook airframes, each representing one of my futile attempts at a display of competent airmanship. May the cargo rest in peace and its intended recipient live to receive delivery another day.

I will have to see. The ability to create a mark point may not matter though if I can't point the pod to it. I remember that sometimes the TGP has CZ available, which typically moves it back to the active mark/steerpoint, and other times the CZ option is not there when I need it, and the pod just wants to look straight ahead. And as someone whose got more hours in the Hog and Hornet, where the pod's available features are not directly tied to the munitions, getting used to this context-sensitive operation is a bit of a curve.

I see, thanks. But what if someone points you to a very specific target among some clutter and you'd like to positively identify it before a guns run in? (A situation I encountered last night) That's what TGPs are for - being better than your eyes at identifying a target at a distance. Removing its ability to do so just because your current weapon availability is different than a few minutes ago is nonsensical to me. There's no way to get the TGP to look at a mark point when no hard point munitions are remaining?

Is there a way to use the TGP when using guns A-G? Once i've exhausted my other munitions, it seems since the TGP is "tied" to either VIS or CCRP in order to use it (inexplicably), it just decides that it wants to ignore the steerpoints/markpoints once I don't have bombs or Mavs left.

Yeah, I just now finished mission 1, after spending a couple dozen hours getting familiar with the Viper first. Ground Pounder Sims campaigns really are top shelf DCS content. I'm really looking forward to the rest.

I was doing some practice missions last night and thought I was going crazy, forgetting something per the TGP. What did you do to get it back online again? Just turn hardpoint power off then on again?

Hotfix: F-4 Phantom mistakenly not released

It's just because someone mistyped that they had 16Gb of ram, when it's really 16GB.

Uppercase vs lowercase. It's the same difference between MBps and Mbps. 1 byte (B) = 8 bits (b)

Which portions of the patch notes are those?

Just like in real planes

Can you keep us up to date here as well? Not all of us are Discord users.

From one of the devs: "everything needed for the module itself runs locally (manual, UI, etc.) without a single byte of data leaving or entering your computer" A browser can be just a viewer, just like a PDF viewer is. It does not need web traffic to operate if it's reading local data. And it seems to me that a light browser reading an HTML file can be less processor-intensive than a dedicated PDF viewer opening a PDF. At least the viewers I've used. They tend to bog down the threads pretty heavily when opening or operating on any PDF of moderate size.

Next week. The 10th is the planned date

Note that the patch status states "planned".

There is though. It is fixed internally.

To be fair, this is just one third-party peripheral that is not working, for a few weeks, and not even for all of the peripheral's users. DCS itself still works. And not all Q3 users are affected.

It is just temporary - it may be different if the components were bricked, but it will be fixed soon. I've dealt with huge bugs in the various DCS builds in the past, just to have to wait for the next patch. It's the nature of PC gaming. Really there's no better option than DCS for a great, authentic mil-sim. Imagine how complicated these things are - the merging of niche hardware and software in order to be able to do these things that we'll never be able to do in real life. It comes with the territory and is d@mn well worth it in my eyes. I'm a real-life (GA) pilot and still spend hours in DCS because of how amazing it is to me.

Not for me. My experience with my Q3 mirrors yours, where it will lose 10-20% of its charge after 1 or 2 hours of DCS while using link. I'd think it's either the cable or the power delivery from the USB port, but then I'm not sure after the results from your meter test may indicate otherwise.

No kidding. My typical pattern is to buy and learn a module if there are good campaigns for it, play the campaign, then move onto the next thing. I started the Viper because of the Ground Pounder Sims campaign. I consider myself to have been pretty well versed in each of the Hog, Hornet, and Harrier modules at some point, (or at least well enough to complete multiple paid campaigns in each) but nothing has had me as confounded at the sensors in the Viper. I've gone through the training missions twice now, and still there are occasions where I am just flabbergasted at trying to figure out what the heck the targeting pod is doing at times. Some of the SPI and targeting logic is just obtuse.

I just took the headset off, alt-tabbed out of DCS, then Print screen key

For what it's worth, the headset itself states v62. Just last night I turned off auto-update in the headset.

Yes, it is in my original post above (I am not at my PC at the moment) I have a Quest 3

I as well haven't experienced issues. Running MT. Oculus software v63, headset still seems to be on 62 though. dcs.log

I went from a G2 to a Quest 3 and I consider it an upgrade for sure, in most ways except for comfort. The lenses are much better. And strangely I don't seem to be affected by the recent Oculus update, but I do know that there are many who are.