Hiromachi

No, not yet. It's a summer so it's not an optimal time for an update, I'm just finishing my holiday in Japan but guys keep working. I will let you know when something new appears :)

I can't imagine why you feel underwhelmed since company made no indications that this chip will be a killer. If some people overhyped themselves then they can only blame themselves. As for the chips themselves. 3900x with proper memory tuning will keep up with 9900k except for some very well binned chips giving you 5.2 Ghz. I want to see a reviews of 3800x vs 9900k with matured BIOS as this one caused problems to all reviewers I've seen so far and properly tuned memory.

Can't recall any promises to surpass Intel. They certainly suggested being on par but surpassing? They do in multicore for sure but not in singlecore. Also, it still seems that RAM is extremely important for Amd :

Yes, Phase I of the cockpit update is meant primarily to adress VR issues as it was created at the times when VR was not yet a thing.

Will get on that one as soon as I find a moment.

No, this time around pilot is forbidden to bring BBQ and soda on board.

Ok, I have tested it in Quick mission and in Mission Editor, works for me every time. All three axis. Can you provide some details like game branch (OB or Release), logs. Can you also try reseting options for CE2 and binding axis again ?

I will check it and if confirmed, will forward it ASAP.

If you try to operate in Manual mode than you will have to introduce range manually by rotating TDC. If you operate in Auto mode with radar lock than it will adjust automatically.

Will send it to Rudel, he's working on lights right now.

In its entirety ? No. First, because of forum rules, second because I do not know of legal status of the document and its publishing. 15 m of wingspan is still not much. With such a wingspan, pipper will adjust in ranges between 400 to 700 m. I'd say, you should take something with at least 40 m wingspan to really see the difference, as it will work properly at greater set of ranges - between 1800 m to 400 m.

I dont use WEP. Or well, I do once for a 100 - 150 flights ? Like I prefer to have engine power throughout entire flight rather than have that 67" in a combat, but then not come home. And without even touching WEP I've had numerous random failures in last three weeks. Similar issue occured to my squadron buddies. Sometimes it happened in less than 10 min after take-off, sometimes after half an hour and sometimes everything went fine despite running engine at 61" for long periods.

I dont play with radiators. It was not recommended during ww2 and it shouldnt be a requirement. Point I'm trying to make is that those engine failures are peculiar in that engine seizes instantly without a warning, with temps only going up AFTER it seized. I've noticed that needle at air coolant gauge keeps climbing after engine stops, going beyond red limit and to the end of the scale. I've also had a number of failures when I was diving so more than satisfactory cooling was provided.

I've been having a lot of engine failures recently, without even touching WEP. There is not an evening I fly, that at a completely random situation my engine instantly stops. And before anyone says something about mismanagement or overheating it, I've been flying this thing for 5 years, I dont think that climbing at 200 mph or cruising at 44" MAP/ 2700 RPM should produce such effects. So I'm not certain that there was a fix in 2.5.5.

To execute an attack on a manouvering target there is a special mode called Gyro-300 m, which basically creates a firing solution for 300 m range for gunsight. It is engaged simply by rotating TDC all the way back (or counter-clockwise, depending from which side you look at throttle handle). Of course it is no perfect, any shots taken at ranges closer or greater are prone to errors but this is optimal for firing at target from up close.

Yes, I have 5-6 real manuals including asp manual. For fast or maneuvering targets Gyro-300 mode is recommended.

So, I just did some testing. Pipper did scale for me. I took An-26 and set 29.6 m Base as estimated wingspan, and pipper started changing at 1.2 - 1.3 km. I also could make accurate shots at 1.1 - 1.6 km for as long as I was flying in a stable motion. There is however certain mismatch, size of the pipper was not exactly meeting the size of the aircraft wingspan. I think pipper scaling still needs some adjustments, fear not, I will forward that. As for the MiG formation, I'm not entirely sure what you were expecting, MiG-21 wingspan is aprox. 7.15 m, which is below minimum size of the pipper (22 mili rad) at any range, so it will not change the size. Radar ranging also works only up to 500 m, below that its going to loose target as its just too close. This gunsight is useful against larger aircraft like bombers, not small and fast moving fighters. Against those you are supposed to use Gyro-300 mode. Last but not least. Angles knob is not operational in Auto mode, it is "disconnected" from the sight as angles are introduced by DUAS-61-14 transmitter. Only in Manual mode it is operational.

Missed that one but as much as I can understand such approach for custom made liveries, there is a wide range of ingame ones that still could be made available such as ones from Blunosed campaign. Having just 1-2 skins is not fun

It should scale 2000 - 300 m, it did when I tested it couple weeks ago when package was assemble. Will check it.

Would you consider expanding your stat page not only to show individual pilots but also squadrons effort ? Recently I've been seeing a lot more groups entering the server and flying together.

Got it, will check it tomorrow guys.

I think it should be both. Just make sure you have proper combination of the settings on the gunsight.

Yes. Back then patch was not implemented with those changes as at the time we submitted them, version to release was already fixed. So they should be working now.

Wait, what ? As far as I remember our Dora has MW50.

Apparently VRR is not meant to show if you have Nvidia gpu and Gsync monitor, as its basically doing what G-sync in Nvidia settings already does. Thats the response I've seen on geforce forums, so I guess no VRR option for us.