Nascar

I've read that the in-game monitoring isn't accurate. The last time I checked it said CPU bound but I wasn't using process lasso. I know I'm running out of VRAM. Nvidia has better performance but I'm tired of the price gouging and low VRAM with everything but the top card.

Does anyone have this set up? I am curious about your performance. I am considering getting the GRE and upgrading to the next XTX when it comes out. I'm using a 2080ti with the VR preset and 2x MSAA. It's playable but not great. Obviously, a GRE isn't going to run high settings but medium settings with decent fps would be nice.

These are old Tom Weiss skins from the Lockonfiles site. I would guess that something has broken with the description.lua with an update. They have worked in the past. They are only partially broken. VMA - 214 BLACKSHEEP worn out.zip VMA - 214 BLACKSHEEP.zip

I finally got around to setting up my PTO2. I updated the firmware and a couple of days later it shows another firmware update. How often are the updates? Did I just have weird timing or does it update frequently? I have a rats nest of USB cables i'd rather not screw with.

Does the yellow chevron symbol mean the bad guys are jamming or just jamming contacts?

Reverb G2 spotting dots off looks good to me. I am still getting a dark line from the lasing drones though. At night I can see the laser and the dark line.

That is the fix for livery makers. I haven't downloaded any Hornet skins and still get the bug. I think we need ED to remedy this.

It works for me. nullPhoto credit Tom Hiatt

Just in case anyone wants to make a skin for it. https://www.facebook.com/photo.php?fbid=7871987336161511&set=p.7871987336161511&type=3

Part of it is the time of day in the mission. Mid-day times will look washed out. The monitor looks like it's set to cold colors. Have you tried changing that? Your GPU is good, I would use MSAA. MSAA is way clearer than the new offerings. At least in VR. I tested the clarity by spectating the Supercarrier LSO spot and comparing the difference in the tower/island. MSAA x4 was superior but was a 15 fps hit.

Maybe, this can help someone or remind me when I forget. Long story short. Plug the USB mouse into the USB 3.1 port. Gigabyte Aorus master motherboard. Long story. I noticed my EZtune CPU overclock wasn't working. Then I noticed the BIOS was very old. When I tried to manually overclock the CPU, I couldn't bring up the BIOS. When I finally got into it, I couldn't do anything. After much frustration, the USB 3.1 port worked. My list of crap software: Gigabyte Thermaltake Corsair

The spotting update would have been a huge success if it worked in VR correctly. It sounds like the update made the spotting the same for monitors as it was in VR previously. I chased down the blimps on the Normandy 4YA server from half the map away using a G2 in 2.8. Now though instead of a single spec off in the distance, things look like a billboard at a certain range. I think when that gets fixed, most people will be very happy with the spotting. As for the Typical aircraft detection ranges in nautical miles: fighter - 3.5, bomber - 6.0 We have had that before, and it pissed everyone off as you were on someone's 6 and they disappeared in front of you. It was just as silly and unrealistic.

The Apache seems to be unaffected.

After the 2.9 patch the planes judder in spectator mode. I've tested it on two computers and VR. They all judder. Spectating was smooth on both of my systems prior to the patch.

How do you revert to the old way?

I'm using a G2 and I thought spotting in VR was perfect previously. The best it has ever been. It was a sharp dot at a distance and now it is totally immersion breaking with a big black square. It's akin to playing with labels on.

As soon as I try to launch DCS, FPSVR shuts down. Is this my issue or do others have the same problem?

The carrier was moving but I don't know about the wind. For the record, I was just curious if the procedure changed with the aircraft weight and not reporting a bug. It was surprising to crash but it really isn't an issue. I try to practice the turn 20 degrees, then back to BRC, climb, and maintain 500ft for 7 miles. Most people I see on multiplayer shoot to 20k ft after launch.

What causes this with a new install and only default liveries installed? The pics are spectating in multiplayer. Is it that they are using a livery that I don't have? I believe if someone actually is using the VFA-32 livery, it shows correctly.

Weird stance. AI isn't representative of the normal flight models. They can stay flying, where you would stall. Launch a Tomcat with full fuel, tanks, 4x 54's, 2x aim-7's, and 2x aim-9's. See if you will sink off the deck on mil power.

Do static units cause problems?

Spectate a carrier in multiplayer. Most of the time people sink when launched.

I saw the gear comment on 10 Percent True - Tales from the Cockpit F-14 Tomcat Sunset - "Puck" Howe. I started doing the same thing with the short burner hit after the second time I crashed.

Yeah, right after I hit the water.

Is it always no burner or does it go by the weight? I know it's so you don't overspeed the gear but I have been launched into the water more than once.