MPK

This the supercarrier at 16x Anisotropic filtering: And the same at 0x Anisotropic filtering: The catapaults and other textures smear but the landing lines stay crisp. The same can't be said for the forrestal at 0x anisotropic filtering: The white landing area lines smear and become invisible ... or should I say even worse than normal. Given that anisotropic filtering can cause stuttering in VR, can you please do the same as ED is doing with the supercarrier module to keep the landing lines visible?

With shadows on, the landing area lines are white. With shadows off, the deck lines turn grey and are difficult to see.

I just upgraded from a 4 year old Intel i9-9900K to an AMD 5800x3D and I thought my results might be useful for someone out there. I went with the older 5800x3D cpu so that I could keep my old RAM and save some money. I swapped motherboard and CPU and kept the rest of the system as is, which includes: - RTX 3080ti - 64 GB DDR4 ram - M2 SSDs for windows and games partitions - Valve Index for VR Settings: SteamVR is set at 200%, or 2848x3168, with the headset at 80hz and the frame rate locked at 40 fps. I bench marked before and after the change in VR using both OpenXR (using the CPU and GPU display in the "advanced" menu), and FPS VR. Since I mostly fly the tomcat, these were done with various instant action missions that come with the plane. I loaded into the 3D world, waited a few seconds for things to stabilize, then wrote down the numbers. Here are the results: As expected the GPU numbers mostly didn't change much, but the CPU numbers have significantly improved. I hope this helps someone sitting on the fence. I am pretty happy with the results and should get another 4 or 5 years out of this PC.

I cannot change external tank textures when changing livery in the latest version. Is anyone else having this issue? I did some experimentation and it seems that the first tank textures that load will work correctly, but then they never change from there. I can even duplicate this it in the mission editor using a load out with tanks, then trying to change the livery:

If I delete the default weapons loadouts with the new rearm menu options they come back after DCS is restarted. This is with the F14 but I assume this bug is not aircraft specific.

See image. A tonne of empty spots but I couldn't spawn on the carrier. Why didn't it just pick a different spot?

I would never join a server that had the new dots disabled, because anyone willing to lower their resolution would have an unfair advantage

This happens regularly in multiplayer, and can affect any of the 4 catapaults. In greyflag, which runs for 15 hours at a time, usually 1 is stuck up by the 15 hour mark.

Can you please remove the rows for items that have "0" inventory? For example, this view should be 4 rows only. Also, please sort the list alphabetically by "type". Thank you!

I don't know if it would be considered realistic or unrealistic, but from a game play perspective, it would be nice if the oxygen was replenished during a rearm. When playing for a long time on a server like greyflag where you end up hundreds of miles from your starting point but can rearm continuously at closer airbases, I seem to run out of oxygen if I spent a lot of the time flying around at high altitude.

Adding my 2c ... this problem happens 100% of the time in single player for me, but I have never seen the issue at all in multiplayer.

If you have hydraulic damage: - The landing gear won't deploy, however the landing gear sound still plays when you lower the gear handle - DLC won't deploy, however the DLC deploying sound still plays when you hit the DLC engage button

At night, the ground crew use the glowy stick things and you turn on external lights to signal for a catapult launch During the day, the ground crew use hand signals and you use the "Salute" option on the "Ground crew" menu. However, there is a short window around sunset and sunrise where the ground crew are using the sticks but they do not respond to external lights, you have to use "Salute" on the ground crew menu. It would be really nice if this was consistent ... i.e. any time the ground crew have the glowy sticks, always use external lights. When they are using hand signals, use the salute menu option.

Adding this from my DCS log file. It clearly received a list of servers but didn't populate the displayed list. I tried again in the single threaded exe and the list is full. Multithreading UI timing issue perhaps? 2023-09-07 01:49:09.578 INFO Dispatcher (Main): //=== END OF INIT ======================================// 2023-09-07 01:49:09.580 INFO EDCORE (Main): (dDispatcher)enterToState_:2 2023-09-07 01:49:09.604 INFO EDCORE (Main): (dDispatcher)enterToState_:3 2023-09-07 01:49:09.604 INFO LUA (Main): Lua CPU usage: metric: average game loading: 41.1161 % 2023-09-07 01:51:43.586 INFO ED_SOUND (9124): Using SSSE3 for peak calc. 2023-09-07 01:51:43.608 INFO ASYNCNET (Main): client has started 2023-09-07 01:51:43.608 INFO ASYNCNET (Main): Using LEDBAT for UDP congestion control. 2023-09-07 01:51:51.439 WARNING ASYNCNET (Main): Ignoring duplicate request to dcs:serverlist while one is already in flight. 2023-09-07 01:51:58.618 INFO ASYNCNET (Main): got 1583 servers from the master. 2023-09-07 01:54:22.677 ERROR VISUALIZER (3060): xrEndFrame failed with error: XR_ERROR_TIME_INVALID 2023-09-07 01:54:34.303 WARNING LOG (8372): 10 duplicate message(s) skipped.

This happened to me just now. It was fine yesterday, so not due to any mod or DCS change. I was still able to look up the desired server IP and connect directly.

Telling numb nuts to select GBU 24 paveway III bombs null

This is on the Grayflag Persion Gulf server. I was distracted while I had the F10 map open and I noticed that the mouse cursor was stuttering. When I brought up the FPS indicator I saw this: null

When on the ground, if I move to the back seat, when I move back to the front seat the trim position will be completely changed. It looks like it alternates between 2-3 degrees nose down and about 22 degrees nose up. If I go to the back seat then immediately push "F2" to go to the external view I can see the horizontal stabilizers moving.

I recognise that image ... this is after ejecting from an F14 and jumping into a hornet: null

See title

To the OP: I use a valve index and have the same experience. For me: the single threaded exe has average to bad frame rates and mild but annoying stuttering, and the multi threaded exe has excellent frame rates with horrifying stuttering, particularly the terrain which looks like it is rendering at 5fps. ED has gotten something very, very wrong with this implementation in terms of VR. There is nothing we as players can do except go back to the old exe until ED sorts it out. Someone on Hoggit suggested that different parts of the scene are being sent to the video card at different rates which is causing all the problems, and as a result this might not be fixable until Vulcan is ready (in autumn 2037).

This is with the single thread exe. When using "direct head control" to move the lantirn point around from the front seat in VR, the image of the large circle is in a different position in each eye, which makes it appear as if there are two large circles.

I have had this issue since the new clouds were introduced 2 years ago. It originally affected 2D and VR and was fixed for VR only, it was never addressed for 2D. Please address this ED!

This is in a multiplayer server. The AWACs/datalink correctly showed it as enemy

I had this happen tonight while playing online. I took damage to the right engine, landed, repaired, and then the engine that was damaged would not start. I had plenty of fuel left, so I know it was not that. I don't have a track file unfortunately, I have tracks disabled as they cause stuttering in long sessions.