Buzzer1977

The Forrestal made a tour thru the Mediterranean with Hornets in '91

E2D crash into each other while taxiing on Forrestal. Bug.miz E2taxicrash.trk

F-14A is rolling from ramp onto CAT1 on CV-59 and then does nothing. F14Block.trk Bug.miz

Having a AV8b on the Forrestal blocks launching F-14s, even if the AV8b is set up to start from ramp, it sits on the runway blocking CAT3. AV8bBlock.trk Bug.miz

Hmmm how large should the pagefile be with 128GB of RAM?

Just watch the LTF 5b Torpedos how they jump out of the water about 20m. They shouldn't do this. They also should burst into pieces when hitting the water with Mach 1 falling from 10km. Track and picture added. JumpinJackFlash.trk

Does this solve the problem with the permissions popup on each start of SteamVR ?

My ticket with SteamVR got closed by Steam after i refused to reinstall Windows to fix the problem with the permissions popup. I have the feeling that Steam has 'larger issues' [sic] with all kind of PCs running SteamVR ...

All this should be in the Handbook, but where ?

I'm struggling with the F-14 AFCS autopilot. IT sometimes engages when pressing the NWS button, and sometimes it doesn't(A/P ref light stays on). Some times after disengaging it via the stick paddle, i can't turn it back on via AP engange on the AP panel (A/P ref light stays off), even if i'm within the specified "within 30° pitch and 60° roll" of the handbook. So is it a bug, bad documentation or am i just too stupid to let the AP fly the AC?

Well, i think ED should evaluate this first

Too early It was way more stable with MXP turned of, but not stable enough. First crash with XMP disabled after a 3-4 hours without crash. With XMP it crashed every 10 - 15 minutes into a mission. dcs.log-20211022-233127.zip

"XMP Certified - Module was programmed with profiles that have passed supplier tests for the CPU and motherboard." The Modules i have are XMP certified with my board and CPU, that's not what i would call 'Overclocking', it's DDR4-3200 MHz RAM with the specified JDEC timing of the product.

Problem solved by disabeling XMP. Don't know what's going wrong there, because i don't do overclocking, just set the standard RAM parameters via XMP. Something with the latest open beta is doing strange stuff it seems.

Switching back to stable and then back to openbeta will take 1-2 days to download with the crapy internet connection i have. So that's not an option. I'd rather live with the crashes for some time and hope that the issue will disappear as it arose with the next OpenBeta.

Deleted the Scripts folder, but it crashed again .... dcs.log-20211021-230220.zip

Also with reduced graphics in the F/A-18c it crashed. dcs.log-20211021-212643.zip

Verified game installation, no bad files. I'll give it a try with reduced graphics settings. It now also happened in the F/A-18c. Took more time then in the F-14 to crash, but it did. My first thought has been it's F-14 related, because it happened most often on typical AC related stuff like jester calling 'bingo fuel' or on touch down. But now it just crashed on flight in a F/A-18. log is attached. dcs.log-20211021-190630.zip

... feature. Like the "Part of coalition in zone" trigger, it would be nice to have a part of coalition in moving zone. F.e. to have a ALARM zone around a carrier or a ship.

I've already sent the error reports with the diag tool.

Jeez ... You don't have to be a Nobel price winner to do the intellectual transfer function ...

Not gonna open my Hotas for pics, but i put it on the rods all around with a tooth stick. It doesn't need much.

Adjust tension screws and silicone lube.

NASAMS C2 and SR are unable move on their own.

NASAMS works fine against airplanes, but just ignores helicopters. Track and mission attached. NoAAvsHeli.trk TRAINING_MARINAS_CN.miz