exil

Arbeite mit den zoom Stufen und dem LMC (linear motion Compensator) am left hand grip vom TEDAC. Grob ins Ziel gehen mit der niedrigsten Zoomstufe, dann LMC aktivieren, ausrichten, fertig. Solange dein Pilot einigermaßen koordiniert fliegt, bleibt dein TADS auf dem Ziel. Laser an und fertig

So, simply uninstall everything, run a repair (long version) and restart your pc. Then install wmr again and follow the instructions given on the first page of this topic word by word. Maybe restart your pc once you've installed wmr again (can't remember if I did that).

Jeez, I have just read my post again. Sorry for the bad typo. But you got the point...

What worked for me was to deinstalle WMR and everything correspondigly (OXRDT, OXRTK, dcs clean repair) and reinstall everything.

Just copy and paste the three files over to your bin again and you should be fine.

I really don't know. I just assumed since I have 32 GB to set the page file accordingly. I now have set it to 16gb and tried a quick flight of around 30mins yesterday. So no reliable test on my side. I'll try to fly a longer mission today and will see what happens.

Versuche mal, die Texturen auf Medium zu stellen. Das hats bei mir getan. Selbst im Apache gehen nun 30 FPS mit repro low level über Incirlik.

Thanks for the reply! I forgot to mention that it mostly happens when I look at the F10 map. I can literally hear the fans of my gpu spooling down when it happens.

Don't want to hijack your topic, but I guess I have the same problem here. I have 32gig RAM and already set the page file to: 32768 32768 But as for now i still get this weird fps drop after 30 - 45 minutes. It'll stay for a few minutes and then everything's back online. Really don't know what else to do. How exactly did you set your page file to? And if I may ask, on my pc windows is on the C drive, while DCS is on the D drive. I only set the page file for my C drive. Hope this is correct?

Got it. Working like a charm now. My Moose wasn't up to date. Really awesome and a lot of randomized fun! Thanks for your effort!

Thank you for this wonderful script! I am trying to implement it on our server mission. But whatever I do, I can't get units to spawn. I see the F10 menu and get a message that I am assigned to a heavy or light task, but then nothing else happens. I precisely checked the naming of troops and trigger zones,but no joy on my side. Anyone with the same problem?

Genau so! Gerade letzteres würde ich für eine bessere SA empfehlen. Daran denken TADS auf der VID Page zweimal anzuwählen. Einmal über R4 (R5?) und dann über T5. Wirklich ein super Feature!

If anyone has troubles with the apache only, try to set your textures to medium (not terrain textures). Helped me to finally have my problem solved with openxr and reprojection.

Umm, did you see my answer above?

Are you sure you have released the parking brake? I know, dumb question but I noticed a tendency when not releasing it.

Try the following: if not done already, run a repair (slow method and delete extra files if it finds any). Then put your headset on the desk, close everything. WMR, any openxr tasks in the task manager and of course steam. Then (before putting on your headset on), start DCS. Put your headset on again as soon as the DCS load screen starts. Notice, that the WMR menu will open and close twice. That does the trick for me at least. Try the following: if not done already, run a repair (slow method and delete extra files if it finds any). Then put your headset on the desk, close everything. WMR, any openxr tasks in the task manager and of course steam. Then (before putting on your headset on), start DCS. Put your headset on again as soon as the DCS load screen starts. Notice, that the WMR menu will open and close twice. That does the trick for me at least.

I think someone mentioned a few pages ago, that FFR doesn't work with AMD cards (yet). But I could be wrong. Yes, page 20 answered by @nikoel

Just to pin the problem down I would try different locations with different aircraft. Not that it helps you with the F14 though. I am absouloutly happy with every aircraft I own except for the apache. So, for me that means currently repro off for the apache and on for every other aircraft. But the problem sounds very similar to mine. My GPU usage went down to 35% when the FPS drops to 20 and it won't come back again. Only when I change aircraft and wait about a minute it'll stabilize at 45 or 30 fps.

Just to pin the problem down I would try different locations with different aircraft. Not that it helps you with the F14 though. I am absouloutly happy with every aircraft I own except for the apache. So, for me that means currently repro off for the apache and on for every other aircraft. But the problem sounds very similar to mine. My GPU usage went down to 35% when the FPS drops to 20 and it won't come back again. Only when I change aircraft and wait about a minute it'll stabilize at 45 or 30 fps.

On which aircraft did you try it? Because I have the same issue on the apache. All other aircraft are working flawless.

Have this problem too. Just close WMR, make sure steam is not running and close all processes via task manager that correlates to OpenXR. Then start DCS, and then put your headset on.

No not really. Thrust doesn't really change, because the remaining engine will deliver the same amount of thrust as when aeo (so basically twice the amount) . To deliver that, you sort of need twice the amount of power from the engine. What does change is NR. It will decrease slightly and therefore you would have to compensate with a bit more collective for that lift loss. But that's just a tiny bit. Basically what you are describing would be an decrease in Rpm. For a decreased RPM you would need to compensate with a higher aoa (increased collective) to compensate for the lift loss. But RPM doesn't decrease (significantly) when in oei.

Thanks for the answer! Well, not that it matters much, but I'm a real life pilot flying commercially. It's just a matter of physics and load distribution. With both engines operative the load both engine have to bear (expressed in torque) is equally distributed across both engines. When one fails, the remaining one has to bear the total load alone. That means the double amount of torque (which is usually taken from the input shaft from the engine to the transmission). It is common for every multi-engine helicopter. The Apache should be no exception here. As a rule of thumb you learn that during your hover check, double the amount of current torque displayed to know your single engine performance. I am pretty sure the SMEs will confirm that.

The no trim option is there for pedals.

Could you try any another module (except the AH-64 and the MI-24)? I found that it's specifically the apache on my side, that is faulty when it comes to repro. All other modules were fine.