toutenglisse

:thumbup: thanks, I enjoy the M2000 much and that'll be the final touch for really being in the cockpit.

Hi - big performance drop when encountering large aircraft formation is due to "turbulence wakes" option (computation impact of many turbulence wakes crossing each others). Prefer to disable this option when playing this kind of scenario.

LOL isn't that synchronicity ?? https://forums.eagle.ru/showthread.php?p=4153658#post4153658 Joined the modded Views.lua for the A8 Views.lua

Hi ! please modify the Mods\aircraft\FW-190A8\Views.lua file for the part defining the HMD view when entering cockpit. (Snapviews #14 --HMD view) Actually the values are the same than the default view (intended for 2D use, where you want the reticle to be centered with hud glass) : out of center for "Z" coordinates. VR needs a centered view for "Z" coordinates, so the point of view is centered in cockpit and the reticle is centered with hud glass for the right eye. So changing this : [14] = { --HMD view x_trans = 0.115, y_trans = 0.055, z_trans = -0.039, }, into this : [14] = { --HMD view x_trans = 0.115, y_trans = 0.055, z_trans = 0, }, Actually I do it with Jsgme and a modded Views file - It's needed to be set by default IMO. Because Always Moving POV to right when entering cockpit, or using a modded file is not best. I don't illustrate with a JPG because mirror is left eye view so you don't see that with modded values the right eye is aligned with hud glass and reticle.

yes "AND" is implied - if 2 conditions set in a trigger occurs and the trigger doesn't do the action, then something is wrong somewhere but not the AND that exists by default between the 2 conditions. 6 - second occurrence : 2 similar triggers : first one in "conditions" you set "if flag #X is false" then "action" : set this flag #X to true. Second trigger same than first but you set "if flag #X is true" then "the action you want to happen on second occurrence". Regarding IF statement, when you set a condition in the middle column of triggers, the IF is implied ? or I don't understand ? (most certainly!) - btw IF or THEN functions are available through lua Scripting. 2nd btw : thanks Suntsag for your M.E. videos and missions !

Yes it cuts black bars left/right - up/down. Even with 0.9 by 0.9, when looking strait forward I can now see a box. Bad. (looking at borders of lenses I don't see it but forward it's obvious) In this kind of tweak, what Kegetys did was much smarter than what Debug Tool does : round rendering zones instead of rectangular ones, so only invisible corners were cut off while sides (up/down - left/right) were rendered fully. But the rendering zone tweak by Kegetys is sadly not available alone, but also with shaders mod that gives perf but takes good DCS visuals at the end...

Regarding the Normandy map, I bought it this spring - mostly because update was announced, knowing at that time the perf were bad - and didn't fly much over it because stuttery/bad fps at low altitude. After update, the map is absolutely OK, very good perf, much nicer textures and scenery objects, I made myself the remark yesterday that if someone doesn't like the map as it is actually, it's because he/she doesn't like this area/geography. The map is rich in details, and runs great. Nothing to criticize negatively about the map.

By far the best performance tweak I made since a long time for my air-cooled system ! … The gpu was full of "dust" (I call'em sheeps) , rad and components between plates, same for cpu rad… All temps went down by 10°c at least and OC frequencies back again to max and stable under full load.

A kind of "less beer costly" feature !? :megalol: !

Probably system dependant - win version dependant. Launching Mustang's registry file doesn't change the values as in his screenshot (same on a friend's system with same actual windows version) + the missing line is not added (no way to add it in fact). So I've not being able to run exact same registry state than Mustang's one - in this case I don't consider that it doesn't work, but that I can't test it. During testing I've noticed VR mirror in fullscreen gives some 2-3 fps more like others said, but since a time I always put mirror in fullscreen so I don't loose DCS focus by clicking outside mirror despite mouse being confined.

Good tip to know. It works with Rift CV1 (more "natively" than with Rift s in sense that enabling 30Hz ASW gives 30Fps with CV1 instead of 27 with Rift s). Of course it gives more ASW artifacts than with a 45Hz ASW, so it's a personnal preference in relation with system's performances - I prefer 45Hz ASW with much less artifacts. And replacing 30Hz by 60Hz in the command line doesn't work. First step working is half refresh rate (45). BTW thanks Scarface03 for the tip.

I just tried enabling motion blur (in Vr) and the effect is permanent (without motion).

BIG thanks to ED ! So many good things listed in the patch note. A very good surprise ! Also BIG thanks to Ugra Media ! Silent but awaited Normandy update is there.

The hard center on the Warthog is defined by the 4 small springs that are below the clutch. They are the ones that counter the big upper spring's force to leave the center. (Moving clutch up) These default 4 springs are ultra weak (compared to big upper spring), resulting in a very hard center - you need a big force to leave center, so small corrections are a problem. I replaced them by springs I made from a long spring, with a much bigger wire diameter, but same inner spire (turn?) diameter (about 6mm). Cut 4 springs and defined height by testing. (you need not too much counter force, or these springs won't let the clutch go full down position, which results in loose stick in neutral position. But just enough force for, at the same time, letting clutch go full down, and only need a small/weak input force to leave center). Of course resistance of the 4 little springs is in relation with upper big spring. If you change the big spring (to change the general resistance of the stick for full travel) you need to adjust also the 4 little springs. I did that day 1 after receiving my warthog. And since it's a soft center, perfect for me ("desktop" position use, no extension).

I compared performances in VR (VR test : 30s flight strait forward in "TF51D Free Flight Tibilissi") Exact same Fps (62 stable in both cases) The GameDVR-Enabled set to 0 didn't kept the value after rebooting until I unchecked it in Game bar windows setting also. The missing line (FSEBehavior) I didn't add it, only modifying the lines I have in common. After test I re-opened Regedit to be sure the values were still Mustang's ones. I guess in VR the Mod makes no differences (also seeing other's VR results) probably because VR manages its own fullscreen and Vsync ? ...

Thanks Lenux. I just made a screenshot of "GameConfigStore" part of registry, showing actual values to put them back to default when I want. Mod is simply right click on the line / modify value by 0, 1 or 2. Noticed that on my registry there is a line missing, comparing to Mustang's screenshot (GameDVR-FSEBehavior)

Hi Mustang! Is there a way to cancel / reset this registry mod ? (Simply for testing purpose or if any trouble)

From DCS WE News : "We will also include the needed voice over files to support all aircraft types that have flown from a Nimitz-class aircraft carrier, including the F-14." https://forums.eagle.ru/showpost.php?p=4010807&postcount=211

No I didn't. (I don't have the Campaign, still only the sample mission 4 I think)

If you have perf issue when big bombers formation is flying near you, be sure to uncheck "wake turbulence" in DCS settings. Multiple bombers' wake turbulences crossing each others hit the perf to single digit fps in VR. Without this option it's Ok.

SA-10 is S300. I don't think AI would accept to engage with harm or other ammo. It's more a target for cruise missiles. (long range detection and shoot zone)

Aurelius what you said is wrong : the part you show is decorative round plate - the real opening of top of gimbal is inside of that and is a square with round shape on the corners (of radius of stick shaft). The movement limits of warthog is a square see it in pictures joined (limit right, limit down and limit down/right)

I post here because it's the same problem. My AI wingman in F18c took off from Lar airbase, turned right and crashed on mountain. I suspect maybe a "panic" move in relation with a not far SA15 that spawned before AI WM took off. But the crash on mountain is probably bug. I wondered if he had been shot down at start until I watched replay. Long track joined, but mission started at 7h00 and he crashed at 7h07-40s. Track is already polluted by my time-acceleration commands. EDIT : in fact track is short since I watched it and exit... WMbug.trk

In VR and with night lighting, I see 2 little bugs : The Watch backlighting, on the left border of cockpit, is only visible in 1 eye (left) - on the right one the Watch is not backlit. There are blocky shadows on inside borders of cockpit, not the same on left or right eye, that rotates with head rotation. Very difficult to see on mirror screenshot but here is one. EDIT : much better with nvg.

I agree with you AND I'll add (because Eagle Dynamics already answered) : Those who want to give money to support ED : (I guess you already have all modules) 1) Buy a module 2) Open a thread "module giveaway" write in it "first to post here I'll give the name to ED and transfer this module". 3) That's it ! (do that as often as you are comfortable with !)