Cathnan

I think I had this problem before. Resetting everything but the licence got it to a more bareable state I now have a problem that's not exactly the same, but similar. Every time I want to transmit, it immediately stops listening, and only after I start transmitting again it would listen.

Damn that would really suck if Vaicom would disappear. I hope it's just a major rewrite or something along those lines like Skatezilla's updater. However, yes would be awesome if ED would integrate it as part of the core

This sounds exactly like what I'm looking for. But am I understanding that correctly? I have to add a condition to, for example to autogenerated waypoint actions. Like I set time is more 08:10 to the CAP Waypoint action, and it'll come alive at 08:10 local mission time. Is that correct? I found it. I didn't realize triggered actions are their own tab. Never payed attention to that before. Thank you

Hi, I want some AI planes (not statics) to spawn on mission start. But even if they have no waypoints, they taxi to the runway and take off. Is there a way to have them spawn and simply stay on the ramp until a trigger is activated or something? I know there is late activation, but I want them to actually spawn on mission start and just stand there. And not have them spawn in later.

In the last big patch the Hornet radar gained the ability to lock helos in ACM modes. It's been long standing now, that it can't detect Helos going below 100kts in RWS or TWS. No matter the settings. I always thought this was a bug, but it's been so long that I wonder, could this be how it's meant to be? Can anyone clarify if this is a bug? Or is this how it's supposed to be and they simply get filtered out as clutter.

Would it be possible to add a keybind for Parking Brake on and one for Parking Brake off. Each would turn and pull, or turn and push the switch in the cockpit respepctivley. This would be beneficial for people with an Orion 2 or similar throttle which have switches for the parking brake that simply say on/off.

These are the versions that fixed the problem for me in SimApp

A little update from my side. I was provided two Firmware Files of what presumably are upcoming versions. I have yet to test in DCS but in SimApp it now works as advertised.

I have the same exact problem. Assembled it, connected it, everything works just fine. Updated the firmware of the handles and the base to the latest through SimAPP and the Z-Axis stopped working at all. I also opened a ticket. Fingers crossed for a quick fix. Was really looking forward to this throttle. For those guys out there with a working Z-Axis, what firmware version are you running on the handle and the base?

I too have many modules. Silly little me thinking after getting the Hornet, Dora, Shark and hearing about the Eurofighter, that the Typhoon would be the next modue I buy apart from maps. I've decided be pleased with getting a general grip on most of the modules, so I can pick up startup and weapons employment with limited time spend on reading manuals when I take one out every now and then. And get properly proficient with 2 or 3. So far that worked quite well. I'm reasonably competent in operating (not necessarily fighting in ) the Hornet, and want to make the Apache my main Helo. Once the Typhoon comes out it'll get the special treatment too, so I can relive my EF2000 childhood dreams . P.S. @Heatblur, ED or other third party devs, Iceland map when?

Thanks . I think I saw a screenshot on Hoggit, and didn't remember where it was taken from. I skimmed over the thread, but didn't see this post

I don't remember where it was but Razbam apparently confirmed that they will make instant action missions for their modules. For the other modules it's up to their developers, so ED for Hornet etc.

What setting was it exactly? I'm having the same problem, but don't find a PTT setting that could be the culprit edit: Nvm. for some reason my mic volume was scaled back to 0, which I never do.

Wouldn't be surprised if the two weeks thing was accurate this time. IIRC the updates tend to be relased in the last third of the month, and I think it's fair to assume it'll be released with the patch this month.

Awesome. That was it, thanks. That would have taken a while to figure out.

I wanted to fly the Apache after a week or two of a break, went through the cold start, accelerated to crusing speed hit trim and let go as usual (center trim). Except this time the Apache imediately started to pitch up a lot. I was going somewhere between 90 and 110 kts. I checked bindings, all fine. Exited and launched the IA mission hot start on runway Caucasus. It's the same. The control indicators UI Overlay shows the trim get's registered. It seems it's simply not acted upon by the helo. The second mission is where the track is from. AH64 Trim bugged.trk

this is the guide I used to set it up. There is also an extension called performance toolkit that gives you control of it from within VR. It's linked at the end of the first post in this thread. I'm not sure what actually works in it, since it seems to be in rather early developement. But I think in this version FFR and FSR do work. I have a RTX3080 Ryzen 7 3700x and 64GB RAM. And as I said, with the same ingame settings I can leave everything else that boosts performance off and get well playable framerates in my tests so far. I have yet to test in really demanding missions to tweek settings, but I won't go back. That's for sure.

I have a G2 as well and recently played around with openXR to cut out steamVR. And I must say that's a difference like night and day for me. I had the VRPerfkit running with FFR and resolution at 60% in steamVR. I get the same or more FPS now with openXR at full native resolution and without FFR. DCS settings stayed the same. And that annoying flickering on the loading screen is mostly gone (Don't know if that's a general problem). I have quite a beefy computer, so your mileage may vary, but it's definitley worth a look imo

The only one for which I would say I regret it - sort of - is the Gazelle. That has nothing at all to do with the Apache tho. I somewhat knew what it was like and that it wasn't really for me and still bought it. Lack of skill in making purchase decisions I guess. It's a fun twitchy chopper, but really not for me. For the others, KA50, Hind, Huey no regret whatsoever. Looking forward to the dorgunners in the Hind. It's a beast as it is, and very different to the Apache and Shark, but dorgunners will make it even better. Don't have the Hip yet, and don't think I'll get it.

That's funny, I took it out today for the first time since the latest update and got this picture in "Through the inferno" SP caucasus. Can't remember the last time the Hornet radar saw something that far out, let alone soft lock it no problem.

In the AH-64D Mini-Updates thread are transcripts for, what seems to be, all tutorials Wags made so far. That's probably a good source if one wanted to make a list.

Amen, well said

I have no problems reading the ddi. Sand that is with a G2 and stream vr resolution at 60%. What Is your setting of "Res. Cockpit displays"? I've set it to 1024 each Sent from my Pixel 2 XL using Tapatalk

I wonder how much being able to use the HMCS of the hornet on one eye is an indicator. I struggled with it at first because I couldn't focus on it properly, but that's no problem now. How different to that is the Apache monocle? Except for it being more important than on the hornet Sent from my Pixel 2 XL using Tapatalk

Sounds like an interesting concept, but I don't think this is practical for the vast majority of people. Even if you can run it on an older slower machine, I doubt the majority of players is willing to, or has the hardware lying around to setup a second machine. It also adds additional complexity software wise, because it's additional code to maintain for what is most likely marginal gains once multicore is released. Or do you mean the physics calculations for the AI? That could really give a performance boost if not all calculations are offloaded. But I still think it's not practical for most people.