Mandoble

have you tried to touch minimaly the pitch with your stick up or down at 1000 feet, 1100-1300 kph? BTW, might be the real aircraft behaves this way, I have no data at all. And yes, Rita is bitching histerically most of the time except in level flight.

Tested FC3 Su33, Su27 and Mig29S, didn't find that issue, I mean, not just piching a bit up where you need to trim the nose down, I mean like scaling up quite noticeable pitch up. Perhaps because the extra acceleration. Will try to test it a bit more later and compare again with FC3 Su27/Mig29. EDIT: Tested again, same results. This time I compared only vs Su27 at 1.0M and above. Of course if you don't trim the Su27 nose it will go up slightly, but then minimum joy pitch inputs have minimal pitch effects. That's not the case of the Mig31 where even with minimum pitch inputs I have noticeable pitch up/down effects and a continuous warning voice.

Great job szcz13, no issues so far (aside of a bit exteme pitching above M1.0)

Have you checked your DCS log file? Does it mention something about core parking? If so, check in this forum core parking solutions (solved the problems to me)

Got it (Beam), so far quite mediocre or even bad headtracking, even worse eyetracking, eventually enough for a truck simulator, but not at all for DCS. Didn't refunded expecting that they will make it work well some day. Anyway you have a demo of Beam in Steam that works for 3 hours, you may test it and then decide.

Suffering similar issue with opentrack: no way to disable/enable it in-game so that POV gets re-enabled/re-disabled. Is that possible at all? Or DCS just disables POV forever once it detects opentrack tracking the first time?

As suggested by Qcumber, I downloaded and installed Parkcontol (which is free). In Windows 11 I created a new power plan with the name "Bitsum Highest Performance" (you can do that from Control Panel -> Hardware and Sounds -> Energy options -> Edit energy plan), then launched Parkcontrol, selected the "Bitsum Highest Performance" from the top dropdown list (it lists all the existing Windows power plans), configured this settings and clicked "Apply". After that I Iaunched the game several times and ran several missions without any stutter effect. So, if you have stutter and you see this line in your DCS log "WARNING EDCORE (Main): CPU HAS PARKED LOGICAL CORES (this can be source of stuttering and reduced performance especially on hybrid CPUs with P/E-cores)" then more than problably this is going to solve the problem (while ED fixes it in the game). nullnull

What do you think was your stuttering cause then?

And that is all behind the stuttering? I mean, disabling core parking solves it? Others recommend to disable hyperthreading from BIOS as well. BTW, might you check if changing the powersettings from Parkcontrol does exacly the change the youtube video explains for the registry?

I'm suffering stutter effects from time to time. A mission starts with stutter effects all along the mission, or the very same mission starts smooth like silk along all the mission, and that happens without changing anything, just restarting or playing that mission again. What I see in the log is: 2025-03-27 09:09:55.849 WARNING EDCORE (Main): hypervisor is active 2025-03-27 09:09:55.849 WARNING EDCORE (Main): CPU HAS PARKED LOGICAL CORES (this can be source of stuttering and reduced performance especially on hybrid CPUs with P/E-cores). My specs: Intel(R) Core(TM) i7-14700KF 32,0 GB RAM Nvidia GeForce RTX 4070 Super 12GB VRAM Windows 11 Pro Then I read this: How to stop cores from being parked? Hello If you want to turn off Core Parking, please take the following steps: Navigate to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\0cc5b647-c1df-4637-891a-dec35c318583. Change the "Attribute" key value from "1" to "0". But also this other way which touches a different value:

And is there any way to have something similar for the Steam edition? i7-14700KF and getting frequent random stutters too. Today, in one session with obvious stuttering, I played with core affinity, disabled CPU 0 from taskmanager and then re-enabled it, and stutters were gone.

What you have is the link to the patch from 2.8.7.204 to 2.9.4.205. So, first download the 2.8.7.204 stand alone version and then apply the 2.8.7.204 to 2.9.4.205 patch. Just extract the zip contents of the patch on the ...\Mods\Aircraft\VSN_F4 folder that you should have after unzipping the 2.8.7.204 stand alone version in the ...\Mods\Aircraft folder. VSN_F4 - pCloud

This is their download page: VSN_F4 - pCloud And their Discord: • Discord | #f-4b-download-links | Century-Series Lounge And there is a new patch (2.8.7.204 to V.2.9.4.205) quite recent, 4 days ago, with the following notes: Patch Version 2.9.4.205 - new collision model - new suspension code - refined 3d-externals (ramps and intakes etc.) -changed afterburner texture/animation - new custom weapons AGM-45A-10 and B-10 - jammer functionality - ATT-Hold Trimm - slightly reduced trim-inputs - refined ALT-Hold-AutoPilot (still not good)

Thanks Tempest, but what I would expect is to be able to do all that easily just from the default group dialogs of the mission editor with no added complexity at all.

Default missions you can easily make are so repetitive (and boring at the end) that the ME definitely needs to include ways to randomize many things: - For each group, allow to define more than one potential unit type/loadout as well as min and max number of planes/vehicles/ships and min/max skill for each one. - For each aerial group allow to defin initial altitude + max deviation of altitude as well as spawn radious from initial location if already airborne or a set of potential airfields for taking off. - For each waypoint allow to define radious from location and altitude + max deviation of altitude. - For landing waypoints allow to define a set of potential airfields. - etc., etc., etc ...

Thanks 342, bracketting the target with the pipper that way is what I try most of the times, but usually with very poor results or no results at all. For straffing, A/A mode is fine as long as you use the bottom of the gunsight as reference and not the center.

I can lower the view to see the sight (A/A) more centered in the hud, but no matter what I do, my gunpod rounds never cross the center of the gunsight. They don't even get into the inner gunsight circle

This mod is a jewel. Best rewarding ever after an AIM7 kill Got a question about head or hud placement, in A/A mode my gunsight (F-4C) is not even visible at 600 knots and 0 AOA and 15 degs nose down (looks like the gunsight is one or two gunsight sizes above the top of the hud) and my gun rounds go there where no gunsight is present (almost straight to the top of the hud and then falling down). Is this behavior correct? And back to the gunsight topic, for A/G mode is there any bombing table with MILS depresion, speeds, alts, etc? Or any good tips for bombing with some accuracy.