Hiromachi

Hmpf. I literally flew 21 last night and gear was working correctly. Did you try to repair DCS or reinstall module ?

As a matter of fact ED is giving us push about F4U and we are obliged to meet certain dates. The issue with landing gear is well reported, known and will be addressed as soon as time allows.

There are no news because development currently demands full attention. But I will try to get some news once time permits.

Will look forward into it Spooky, thank you for reporting!

The person who made the skins had some Pitts and Christen Eagle experience in real life, however since he is no longer with the team, I cannot say what was his motivation or connection to this particular livery.

That depends really. A6M2 and A6M3 were far better aircraft than Ki-43-I and early Ki-43-II. To start with, Zero did not have particular issues with structural integrity while first Oscars delivered by Nakajima at the end of 1941 gave pilots headaches due to bending wings. But over time Nakajima put a lot of effort into improving the airframe. Oscar gained similar to Zero reflective gunsight, armament was increased to two 12.7 mm machine cannons (as Japanese labeled HMGs) and unlike Zeros, protective measures were introduced. By the end of production of first series (Ki-43-I) protected fuel tanks were installed. Ki-43-II gained more powerful engine (same as A6M3 / A6M5 Zeros), proper armored plate and better protected fuel tanks. By the end of the 2nd series and especially with introduction of Ki-43-III, Oscar was a fairly well protected aircraft. Fuel tank protection was comprised of various layers of rubber and other dedicated materials, which likely wasnt as good as U.S. all rubber fuel tanks, but was on pair with German or other nation solutions. And armor protection grew to three armored plates (small one to protect the head, large piece covering back and lower parts of body and another small piece angled below the pilots butt and legs). It was 13 mm thick, but high hardness steel was used which proved in tests, when two .50 cal rounds fired at it dented it, but failed to penetrate. And later Oscars were as fast as Zeros. By late 1943 Zero gained some performance but firepower and protective measures remained almost the same as in early ones (the sole protective measure introduce was fire extinguisher system which could detect fire and in case of detection, would spray CO2 to extinguish flames). Another aspect could be discussed as flight characteristics. Oscar required lower stick force for lateral control producing better roll rate, especially at high speeds. So all in all, I would switch from Zero to Oscar by late 1943 if I had to fly either. Better firepower would be nice but Ho-103 compensates a lot with explosive rounds and its better to have armored plate than not to have it As for opponents and theaters. Personally I am not a fan of rushing to late war designs. Data on late war Japanese designs are limited indeed, but I simply favor early to mid war stuff. I'm pretty sure that decent balance could be created with high levels of realism if something like 1943 New Guinea theater was selected. You can stick there Zeros, Oscars, Ki-61s and even newer dive bombers like D4Y1, while Allies have whole range of aircraft from Wildcats and P-40s, through Lightings, Spitfire Vs and Corsairs up to early P-47 D-2s.

Japanese engineers didn't live under the rock. It makes not sense to reinvent the wheel when optimal solution exists elsewhere. And Revi 2b was considered at a time a fine gunsight that was used as basis for designs in more than Japan. Besides, the same point could be made about armament. Japanese Type 99 20 mm cannon was a licensed copy of Oerlikon FF used in Bf 109, PZL P.24 or bunch of other designs around the world. Although realistically I dont think the statement is wrong. Zero design was of Japanese origin. However what it was furnished with wasn't up to Mitsubishi but IJN. And it doesnt change its origin just as furnishing Hurricanes by VVS with 12.7 mm Berezin machine guns didnt make them Soviet. As for propeller, that's a bit of exaggeration. Constant speed unit in the propeller was based off the Hamilton Standard design (due to acquired licence), which at a time (again) was leading prop company. But propeller blades were designed by Sumitomo Heavy Industries.

As every pilot Saburo Sakai had limited knowledge of the entire scope of air war, being low ranking flyer at a time. His memoirs (but not Martin Caidin reconstruction of them) are good source for variety of events and experiences, but I would not take them for granted for any information. Especially when it comes to organization and unit employment across the frontline. There were Zeros in China. I've written article about that few years ago: https://forum.il2sturmovik.com/topic/27807-debut-of-zero-sen/ It's based on a number of sources, including 12th Ku combat reports and one of its pilots translated diary.

Hey Oswaldo, I will look into that and forward to the devs after reviewing the issue

If there is similar info on FAA roundels and other markings, I will gladly pass it to the team.

A list of generic skins desired to appear in game would be nice. I could forward that to Rudel.

I dont have manual for R-25 engine, but R-13-300 and R-11F2SK-300 manuals used in older 21s indicate the same thing. When SPS installation is ON (operating, so SPS switch engaged ON and flaps down to landing position), afterburner cannot be engaged regardless of throttle position. I will forward this bug report.

Hell yeah! Cant wait for it

Hello, I will investigate this tomorrow. Thank you for reporting.

If that is a separate bug than please make a new bug report.

No, I checked it. It seems that FPS Vr in some reason affects the performance of SteamVR causing it to increase the usage of resources. I deleted my FPS VR and ... its miracle but it worked.

I know. What I mentioned in update was reflective of prototype and features in general, details specific to this variant will be reflected properly.

Hey Schmidtfire, I will forward you're request

Well, card is not pos, it has performance in it. It's software that sucks. I went with indicated above config online. Well, its playable but there are still reprojection errors related to warping (text, gunsight) and shadows flickering. And reprojection is Valve concern if I'm not mistaken.

I just set motion reprojection to SteamVR perr-app setting in OpenVRSettingsUX.exe (can be found in Steam folder). I can try changing it to Motion Vector. No, not particularly. But than again, I wear glasses and until my lenses from VROptician arrive, I am not the best judge of how blurry or not things are.

So I have changed: - Default SteamVR app motion reprojection mode to SteamVR perr-app setting - Force DX11 mode - ON Motion Reprojection works MUCH better for me and its actually holding to 45 FPS at 14-15 ms. There are however still frequent instances when FPS goes up to 50-60 and I see reprojection indicators changing (switching constantly Blue - Red, so GPU / CPU bound - Off), but smoothing also seems to be working and so overall experience is like Nvidia. On the other hand it did not cure on my side issue like text warping. There is also visible shimmering on power lines, cockpit edges (MiG-21 most noticeable on gunsight frame) and even a bit on fps VR window. I cranked up settings in game, set few different things in driver and overclocked GPU. Now I will take it online and see how it compares to my yesterday experience with Nvidia.

So I've tried the above. Unfortunately process killing did not help and Virus might be right, just have to wait for Nvidia to step up. Also, as it seems, turning PBO from Automatic to Enable actually lowered the clocks of the CPU. It seems that AMD microcode in the chip knows much better how to handle new CPUs than PBO which is implemented by motherboard manufacturers.

Yup, exactly the same way I have it. FPS seems to lock itself to 60 or around 60 and it fluctuates but despite it being so high, image is not smooth. Only at 45 FPS when reprojection works, it is smooth. Anyway, I will test it tomorrow since I have to put 6800XT back into case. It's definitely worth trying. Also wouldn't surprise me if it was SteamVR thing. Valve has neglected both Nvidia and AMD launches this year. However regarding usage, thing is that we did tests with Exil with reprojection off to measure pure output. And more importantly, the difference was when window was out of focus vs in focus, as than GPU usage in former case increased for DCS app.

Literally everyone in this thread has issues with new AMD GPUs except for you. Also it is not some problems, its a matter of having pleasant experience. It's not true. I just reverted to 20.11.3 and could not fire up my G2 at 90hz. Turns out such issues were reported couple weeks ago: https://community.amd.com/t5/drivers-software/hp-reverb-g2-windows-mixed-reality-not-working-with-rx-6800xt/td-p/427626 After installing back 20.12.2 headset starts properly at 90 hz. Now motion smoothing might not be important for you or not bad for you, but it is very much for me. Like with Exil, smoothness of image (motion smoothing on AMD causes for me a slightly blurred image) on Nvidia, despite slightly lower FPS and higher frametimes was apparent. I can assure that this means a lot, especially in ww2 dogfights when you try to follow targets. Image has to be clear and smooth. 3080 provides both, although on my end I get occasional very heavy stutters (however those so far can be cured to the point I can keep flying and are acknowledged and worked on by Nvidia). Tldr is that I could not confirm if motion smoothing / reprojection work properly on 20.11.3 because I couldnt launch headset at specific refresh rate. I also cant confirm your performance advantage unless I alt+tab the game. Which defeats the point of having such advantage since it cant be used. Now moving on to other actions. I have received response from Valve and they basically told me that if issue is exclusive to DCS, than I should contact ED. They wanted to have none of it. I checked Il-2 Great Battles series and text warping and reprojection not holding properly to frametime are there too but far less pronounced, perhaps because it is a far less demanding game on a hardware level and so its not hard to hit 90 FPS and stay around 8 ms frametime. But issues with motion smoothing and incorrect GPU usage are exclusive to DCS. And I have no other games in VR to test them, so thats as far as I can go. So I will keep bothering Valve about that since its their SteamVR. But I also asked Bignewy to forward input from this thread to ED devs and he said he did. GPU usage and motion smoothing, and perhaps other problems at this level, might need tweaks on ED side too. I did what Valve recommended. Finally, I've opened ticket on AMD support. But I dont expect any solution to those problems in the upcoming days (due to obvious period of the year) so I will be returning 6800XT next week. Point is that if you want GPU for VR, well, Nvidia is the way to go. On software side its better supported by companies like Valve or Oculus, and Nvidia control panel, as primitive as it is, has some features like max pre-rendered frames in VR which might be helpful. AMD had that feature some time ago but later it disappeared from drivers. And there are no other VR dedicated features in the Radeon Adrenalin driver. Raw performance gives AMD clear advantage, but due to above software issues (regardless who can fix them - DCS, SteamVR or AMD) I am going to stick to 3080 until I can get 3080Ti. It is a shame though because Asus 6800XT LC Strix I have is a fabulous GPU, it clocks nicely and runs very cool. I have not seen any Nvidia liquid cooled GPUs like this. On a sidenote. If you dont care about the curse called VR than AMD is the way to go. Legends about better color reproduction are actually true. I checked that on my 4k 10 bit panel. Furthermore the sharpening slider in the driver actually works and takes almost no performance for a quite noticeable result. On a flat screen I enjoyed gaming on AMD from a visual perspective a lot more than on Nvidia 3080. Not to mention how many cool features AMD Adrenalin has, including built in overclocking tools, framerate limiter, system tray so user does not have to install additional software like Riva Tuner, Asus GPU Tweak or MSI Afterburner. Now AMD has to dedicate some time and resources to VR too.

Well, I've just reinstalled driver to older one but mixed reality portal started having issues with Reverb so I'm reinstalling portal now. And no. Nvidia ain't perfect either. I have severe stutters on my 3080. Issue about stutters with Ampere is known to Nvidia for 2 months but still not solved.