deltaleader

I don't know if this is a Win11 bug or DCS. At the very least I would hope DCS would investigate this problem. There are workarounds which makes me think it's more of a bug. I am guessing it would happen on the the Ultra 285K processor as well because it was happening on my old 10900X processor but only after I updated to Win11 or a DCS update in the last couple of months. Just not sure exactly when it started other than those two changes. When I was on Win10, I didn't notice this problem, although it could have been present.

Sorry haven't messed with all this until today again. I will check for Intel-VT. Not sure if my Intel Ultra Core 7 has this or not. Everything seems different with the Z890 chipsets. But for the most part, DCS is pegging CPU 1 at 100%, other cores are fine. My only real solution at the moment is process lasso which fixes the problem by locking out DCS from CPU 1. Performance seems ok when doing this, so I can't really complain about this workaround.

So I set the core affinity as you described, no process lasso. Launched game, loaded in to a multiplayer server. Just those cores selected were being utilized but none of them were just 100%. Plane loaded relatively quickly. Are those cores considered the P cores that game should be using? I know when I just blocked core 1 that was getting hit initially, everything was fine. I suspect I can just use process lasso for DCS and workaround this problem as I have been doing. I also tried to turn off core isolation in windows, but that did nothing. I don't or cannot find core parking enabled or referenced in my settings per that thread.

When I don't run process lasso, I can never load in to a plane. Here is what my CPU looks like with out process lasso.null I can alt-tab out and launch process lasso and the core recovers, game loads.

I am running this on a new machine I built using a MSI MEG ACR Z890 with Core Ultra 7 265k and 64GB of RAM. All on a new install of Windows 11 Home. The whole P and E core thing is new to me. I did not set up any overclocking in the bios or than setting my memory to XMP profile. I am not sure what is going on with Hypervisor. I did not install any VM's unless Win11 does something by default. I checked my Windows features and Hypervisor is not installed nor is virtual machine platform. I can say when the problem comes up trying to load in to a plane in DCS, one core is pegged and the others are under light use. This also happened on my previous machine using Win11 with an I9-10900X CPU. Once I kill the pegged core with process lasso, everything loads right up. I have seen some other threads here saying to toggle it on and off does the trick. For now I can kill the one core but it would be nice to not have to do that and figure out what the root of the problem is. I appreciate everything looking in to this.

Let me know if this dcs log is good or not. I can try to reproduce the problem and create a new log. This was from my last session. The more I think about this, I think the problem started happening on Win11 but cannot totally confirm that other than it happens on 2 different machines running Win11. dcs.log DxDiag.txt

In one of the last few updates, something changed with how DCS is using multi threading. I have tested on two different systems and each one exhibits DCS loading up one core and not utilizing other CPU cores. I have a new system setup now and it behaves the same way. I have tried the normal DCS World shortcut to launch the program as well as the DCS World MT shortcut. Both insist on utilizing core 1 in this case and very little of the other cores. This prevents me from getting in to a session. My work around at the moment is to use process lasso and block DCS from using core 1. That seems to help quite a bit. My question is, what is going here? Is this a bug or is something misconfigured? Side note: It is possible this started after Windows 11 was installed, but I am not totally sure. I have done clean installs of everything and driver updates. Nothing helps.

Excellent. Thank you for this. That did the trick and got my kneeboard over to the the main screen. So what I have learned from my initial problem is that Winwing simapp Pro does not like screen scaling for size of text, apps, and other items. You have to leave this at 100% otherwise the monitor arrangement will only be recognized in WW from Left to Right.

Attached is the viewporthandling file. I changed the values to what you had but then the kneeboard no longer comes up. Maybe I just don't understand the syntax for this. Also attached a screen shot of my monitor layout. Screen resolution in total is 6144x2160. My main monitor is running at 3840x2160 while each WW usb display is at 768x1024. Let me know if you need to see a specific lua file. Thanks ViewportHandling.txt

I think I resolved the problem. Hard to explain, but I think it had to do with the fact my Winwing MFD displays were organized left to right with the my main monitor being right of the MFD's in the Windows Display settings when it need to be ordered with my main monitor on the left. I also changed my main screen font scaling back to 100% from 125% and this all allowed the pop up window to be visible on the F10 Map. However, this just introduced another problem in that my kneeboard window comes up across my MFD screens and I cannot seem to move it to the main screen. It's becoming beyond annoying to configure DCS. Any chance there is a manual method of relocating the kneeboard window via a configuration file or something I could edit to move it to my main monitor?

Its on. Nothing seems to work. Even repairing the install does nothing.

I cannot figure out why this has been happening for some time now. Doesn't matter if in SP or MP mode or in any mission I load. Used to be able to click objects in the map view during a mission. It would provide details about the A/C, Unit or Airport. But I no longer get these boxes. I can move around the map, click the menu buttons, etc. But not able to click on objects and get the typical information box I used to. It was especially helpful to get airport information or carrier heading. I have no clue what has changed or if there is a setting preventing objects to be viewed. When I check with others online in the same servers, they do not experience this problem so its something on my end, not sure why. I am fully updated on beta. Suggestions??

Thanks. The Mustang is the only warbird I fly. I guess I was not aware of others not able to use rudder for steering.

Rudder does not seem to work on the ground to taxi. I can only use differential braking to steer. Tail wheel is not locked. What I am missing?

I see what you all are saying...scanning and getting visual on threats is the key. Only problem is in DCS, I cannot see other planes unless they are within a few miles. The visual representation in this sim does not seem to be accurate and I do not know how to fix it. In real life I can go outside and spot planes 7-8 miles away easily. But not in DCS :( and I don't really use labels...

Please help me understand if this is correct in Real Life for the Hornet. When an IR missile is launched toward me, I do not get a RWR indication or any indication that a missile is inbound. Is this the way it is in Real Life? If that is correct, then how does the AI aircraft I target know when I shoot an IR missile at them? I know the AI detects it because they instantly start popping flares only once I launch the AIM 9.

I just turn the master arm off.

Hey I don't know if anyone has noticed or not. But the Glide Slope is not implemented correctly. If the carrier is pitching, you will notice the glide slope pitching as well. It should not do that according to RL pilots. It should be stabilized with the ball and lens.

+1 We seriously need this for day ops in overcast weather.

Negative, I don't have either. Any thoughts on how to fix this? I am guessing it is registry problems?

Is it normal that I have to activate all my modules after every update? This has been going on for some time now. Every DCS update that comes out requires me to activate each module. There has not been any hardware changes, etc.

I have messed with this stuff quite a bit. As previously posted, you can play with the curves to find the right positioning for the throttle AB and MIL settings. I opted to just use Target for my Warthog since I use a Joystick offset. But the problem with the curve in DCS is that is based on an "S" curve and what you need is a "J" curve. You can play with the user curve settings in DCS but that was more of a pain for me. The Target software for the HOTAS Warthog solved this problem for me. This is the Target script settings I use and found the MIL/AB detent is just perfect for my setup. Hopefully it will help someone... MapAxis(&Throttle, THR_RIGHT, DX_Z_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetJCurve(&Throttle, THR_RIGHT, 66, 75); MapAxis(&Throttle, THR_LEFT, DX_ZROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); SetJCurve(&Throttle, THR_LEFT, 66, 75);

Done deal...I got it now. Thank you.

Well I just changed the keybinding. So "Cycle Afterburner Detent - ON/OFF" is now "0". Just need to remember to make sure that is off each flight.

I guess I don't get it. I now have to push 0 in order to put my Warthog throttle into AB? I have the AB detent installed on my warthog but there is no simple way to hit 0 and then lift my throttle in to AB. This update kind of does not make sense to me.