Strong05

DX11 forced and reprojection off has netted the best results for me as well. SS at 100%

Would love to see an N variant as well. Agree to disagree. There is more to diving capabilities then the mach limit, as already discussed. Or one could argue it had the flaps because it could quickly achieve speeds other planes couldn't.

Show me the reference that says the P-47D was a bad diving airplane, or that it had bad diving characteristics. If compressibility was so bad on the P-47 why did they remove the dive flaps for the N and M models?

He shows the P-47D max airspeed at 10k ft as well. He addresses all of your compressibility concerns by talking about Mach limitations vs KCAS limitations. The Spitfire has a higher Mach limit but a lower KCAS limit. As previously mentioned on this thread the compressibility problems occur at high Mach not KCAS for the P-47D. Which means that compressibility would only have been a problem at higher altitudes, mainly above 13k ft. So below 10k feet compressibility is not a problem for the P-47. He also talks about, but does not address in this video dive acceleration. Which the P-47D does extremely well in. Bottom line, the top speed of a P-47D in a dive is just over 500 KCAS vs the 450 KCAS for the spitfire, at or below 13k feet. Do you have a reference for the throttle settings you are referring too? P-47's almost always operated with the throttle and boost control linked, pretty sure he even talks to that so I don't know why or how you think he would talk to them being unlinked for a climb. I'm also not sure what your point is by bringing up throttle settings for climbing, it has nothing to do with dive speeds or dive performance.

Enjoy! It's a 9 part series with a lot of references to manuals and NACA data. I've linked the one on dive speeds. Here's a time stamped link to where he says nothing is faster then a P-47 under 10k feet. Of course you will need to watch the whole video if you want to see all of his references to get to this conclusion.

Recommend you check out "Greg's airplanes" on youtube. He has a very comprehensive series on the P-47. That info may help you understand which sim has the more accurate model. The cliff notes from his series (if memory serves): Only the spitfire can match a 47 in dive performance and that's only at certain altitudes bands (up high only I believe). The turbo gives the 47 an edge at altitude over most other fighters. Haven't flown the other sims version, so I will not comment on which is more accurate.

I thought the same too at first but, I was running a much lower SS setting in steam with DX12 on. I turned SS up to 100% and then forced DX11 on and that brought the visuals back up and kept my frame rate up/got rid of the stuttering. It's also possible this issue has been resolved with the latest drivers. I think it's also worth noting, I didn't have these problems when I was running a 1080ti. They only materialized when I got a 6800xt.

You have to access it through Steam VR in the headset. With the headset on and Steam VR launched push the small button next to the window button on your WMR headset controller. This will bring up the steam VR menu. The 2nd or 3rd round button from the bottom left should be WMR settings. The force DX11 mode is nested in that menu somewhere. I've posted a better description previously if you want to search for it, it's been a hot second since I've accessed the setting.

Right now for gaming the 5600X should be better then a 3900X due to clock speed and IPC. It really depends on the game though and how well it takes advantage of more cores. Most games don't benefit much from more then 4 cores with hyperthreading, however this paradigm is shifting ever so slowly in the industry. If you aren't doing productivity or streaming Gamers Nexus recommends the 5600X he believes you really don't need the extra cores, but this also takes into consideration cost. All that said, I doubt you will see much difference in DCS between these two CPU's.

Thank you Bignewy for the update! Really looking forward to this being fixed for MP on larger servers. Right now it's just not playable.

It "works" you just get a lot of artifacts (double images, blurred images etc). To be fair I haven't tried turning it back on since the last bios update, but the update notes didn't mention any improvements in motion smoothing support.

Would also really like to see this addressed.

Really hoping to get this bird by the end of the 1st quarter. It was originally supposed to be delivered by the end of last year.

Here's hoping the BIOS update works as advertised.

motion vector and motion smoothing (both frame interpolation methods I believe) as I understand it are both highly driver dependent. The AMD drivers aren't very good at motion smoothing, when compared to Nvidia. I've turned off all motion smoothing for all of my titles because it's so terrible (6800XT). Hopefully this will get better with new drivers.

Had lots of trouble at first as well. Had to update to the latest bios (USB issues), set steam vr to force DX11, and set PCIE3x in the bios and all is good now. As a side note, the AMD drivers do not work as well with motion smoothing as nividia. I turned it off as there were way to many artifacts.

Oh, forgot about that problem. That sucks.

Try updating your motherboard bios or forcing PCIE3 for your video card to fix your USB problem. This is a known issue with AMD and a fix is due in April via a bios update.

Viper. Love the Tomcat but Jester/Radar kills it for me. I can never get a target lock in the tomcat, and if I were any any other full fidelity module, it would be a piece of cake to get a lock, but all I hear in the tomcat is "sorry can't do that", followed by everything going black from getting shot down.

Thank you Buzybee that finally did the trick. Looks like I didn't move the folders to the correct root folder.

As previously stated, I have tried re-installing and moving the folder that you mentioned per your instructions, all of which is on the sever computer, logged in as the admin/Sorta, none of which has worked. Tacview works just fine on the client computer. Are we certain there isn't some piece of code missing to hook tacview into running with the DCS server? Thanks again for your help.

There is only one user on the computer, which is also the admin. The user "Sorta" is the user name for DCS. I've already tried installing TACVIEW while logged in as the user/admin that runs tacview and DCS. I've also copied over the folder per your instructions and tacview still isn't working on the server. I had to add in some text/code to get Tacview to work on the client side the last time I installed it. Could it be that something like that is also missing here?

I copied the folder over a while back per one of your posts on here. What do you mean by install tacview while logged in? Do you mean with the server running?

Here's my client log. dcs.log And here is my server log. Thank you for your help figuring this out. Regards, Strong05 dcs.log

Nvidia is probably the better option for VR. VRAM is important, but allocated (which is what we see) is not the same as used. Go by performance benchmarks when deciding one what to get. In my case I got AMD because that's what is available.