Search the Community

Hi everyone, I’ve recently started experiencing a sudden and severe FPS drop exactly at the moment my aircraft auto-rotates into the final parking spot on the Supercarrier. This happens with both F/A-18C and F-14, across multiple maps (Syria, Persian Gulf, Caucasus), different weather presets, and even in clean missions with no mods. It’s fully reproducible, and did not happen before recent patches — same missions and graphics settings used to work flawlessly. The log shows the following at the exact moment of the drop: dDispatcher)enterToState:10 DX11BACKEND: render target 'mainDepthBuffer' not found DX11BACKEND: render target 'uiTargetColor' not found DX11BACKEND: render target 'uiTargetDepth' not found SCENE: Scene was removed with 5 alive objects There’s also a missing texture error: KevinWakePattern812x1024.dds not found Happens regardless of module, map or weather - Shader caches cleaned, modules reinstalled; no change - FPS returns to normal immediately if I switch slots after the drop Are others experiencing this sudden FPS drop during the Supercarrier parking turn-in phase after the latest updates? Is this already a known issue or should we report it as a regression? Would love to hear if others can reproduce it too. Thanks! Update: Interestingly, on one flight, the issue didn’t manifest — despite the same weather, mission file and parking procedure. However, the log still shows KevinWakePattern render target errors during FSM 10 initialisation. I re-flew the exact same mission under the same conditions. On this second attempt, the same FPS drop and render target errors occurred again during FSM 10.

Aircraft can only be assigned to takeoff from the runway at Allstedt. Assigning them to Takeoff from Parking or Takeoff from Ramp causes them to jump 20nm to Merseburg even though Allsetdt appears to have 128 parking slots.

Similar to the Peenemunde issue reported earlier, it's impossible to place more than two aircraft as Takeoff from Parking or Takeoff from Ramp at the Altes Lager airbase.

Hi everyone, I noticed that large aircraft (namely KC-135s) cannot be spawned in parking spots 150 - 159 at Andersen AFB, found on the ramp just to the north of runway 06L. This is contrary to satellite photos of Andersen which show KC-135s parked there, and in DCS there's plenty of clearance between adjacent KC-135s (over a whole aircraft width between wingtip to wingtip). As you can see, I'm at the bottom of the list of available parking spaces, 149 is the last one available and 150 - 159 do not appear. Static KC-135s parked in parking spots 157 - 159, clearly showing that there's plenty of space (I can place another KC-135 in between 2 adjacent KC-135s, and still have room to spare): And finally a satellite image showing KC-135s parked in the same area: This also goes for the B-1B, B-52H, C-17 and C-130, all 4 easily fit in the same parking areas, with room to spare, it's only the B-52s that would run into issues taxiing past each other. Obviously the best solution would be for a start from ground option for AI aircraft, and have the AI pathfind an appropriate route to the active runway (maybe it would also be useful if we could define runways for things like road bases), even if we have to define the route for them with a taxi waypoint or something, then if we couple that with optional unit placement restrictions (instead of enforced), and then all parking issues would be resolved forever. Here a camera position overlooking the 2 ramps: -camera 10.453970 0.336106 12.896755 -cameradir 0.874645 -0.394899 0.281160 Incidentally next to parking spot 137 there's an erroneous TACAN antenna, IRL this is actually an ILS glideslope antenna (-camera 10.691929 0.177060 13.149259 -cameradir 0.699083 -0.412004 -0.584411).

When you first spawn in, the parking brake is already on, and you can push in the toebrakes and the parking brake releases. Easy simple, correct. However to set the parking brake, it should work exactly the same as the P-51D or P-47D. Pull handle, depress brakes, release brakes, release handle. Handle sticks out, brakes are set. In DCS currently, the 64 won't follow that operation. I can pull the handle, but A) it doesn't pop back in when I release my mouse from clicking it; B) when I pull it, as soon as I start to depress the brakes it pops the handle back in. It's as if it thinks the parking brake is set just by merely pulling the handle out.