GrEaSeLiTeNiN

Thanks for the update! Trying it out but could not get flares to dispense. CMWS is armed but nothing drops when I press dispense. Update: Works - Check number of chaff (30) or flares (30) in ME loadout.

Halfway through this, playing solo, and it feels like a nice campaign (Needed some help though with Olympus to take over zones and protect them.) Are there other 'Expansion' missions using other maps? I saw Catch'n'Keep (IW Series). I might try that.

When LOBL is on and the hellfire is tracking (solid square), pressing the DELVRY button to get out of LOBL to select DIR/LO/HI is not possible. I have to set the LAUNCH button to STBY first in order to select one of the LOAL modes. But if say a Reaper is lasing the target, it automatically jumps from LOAL back into LOBL again even though I have not locked up any target (see screenshot). Is this as intended? Update: This is intended based on an answer in Discord. I compared it to the Apache. It's actually similar to the Apache where DIR goes to LOBL mode. I can still select HI/LO but to get back the LOAL small dotted box, I had to WAS another weapon like guns or rockets and then WAS back to SAL.

As in title. I can't ever fire a hellfire in LOAL mode even when within minimum range parameters unless I select ORIDE first. Is this correct? (With ORIDE, I can launch them in DIR/LO/HI and then fire the laser and they will guide to the target just fine.) Update: Launching a HF in LOAL with the small dotted box finally worked. I realised it's supposed to be used with DIR or PREPT target locations (PC manual pg 228). Point the MMS to the selected DIR or PREPT target area and the small box will turn solid and you can fire when within parameters. Without DIR or PREPT, the small box will be dotted and the HF can't be fired unless ORIDE is selected. [Just seems a little strange that the LOAL mode would become LOBL as soon as it detected an external laser beam (of the same code) such as from an AFAC. That did not happen with the Apache. So if I wanted to stay in LOAL in the Kiowa, I had to point the crosshairs quite a distance away from the target.]

CTD again when firing a hellfire. ORIDE/NORM/LO mode. Crash log attached. dcs.log-20240830-022501.zip

There is this other mod method that removes the large spring altogether and brings the 4 small springs up. May be too soft for some but modder says you can add washers below the springs or I've read some replace the 4 springs with slightly stiffer ones.

I hope the next patch is a sizable list of fixes. They owe us that after the last two patches were small and nil. I am also wondering what the point is of reporting bugs in the bugs section here. I don't think PC visits this forum often enough. Their discord actually has a section for bugs and it's a long list.

My hotas is on table top so I was hoping the new spring would be a game changer. But unfortunately it's not The positive reviews were probably for ppl who changed it when their warthog was new. I'm hoping with time this green spring will feel softer. You could try the new warthog base. But I read somewhere you'll need to rebind the stick (IIRC) but at least its the same layout. Yes lots of new and better hotas out there but to rebind all those modules!

3 year old Warthog. Decided to get the rather pricey softer green spring by Sahaj to replace the stock spring. Honestly, I couldn't quite tell the difference after changing it. Ok, maybe it's very slightly softer. I think if your stock spring has been seasoned over time (and I could feel it in mine), it's probably not necessary to replace it. Guess I'll have to season this one too before it feels like what I had expected.

What's the helicopter at 0:53? Looks like a fun bird.

I wouldn't say the OP or anyone here is demanding a trial. At the end of the day, consumers will differ in purchasing criteria. I think a module such as the Kiowa, today, would have reined in the undecided with a free trial.

If ED or a 3rd party dev decided on having trials, they would/should have taken into account misuse and genuine use in their marketing decision. Any misuse was probably an oversight on some control measures during trial implementation. Not everybody is familiar with choppers or what they would like or not like about a module. IMO, free trials are fair when ED's business model and sim situation inclines consumers to buy an endless number of modules to sustain their interest. A form of QA at release since module standards can vary.

Yeah, v5.5.X probably isn't working with TrackIR 4 since the download website says: Requires TrackIR 5 Series hardware or newer Windows 10 or newer (I am using TrackIR 5)

Have you installed the mod as follows? Rearm/refuel requires Cayuse to be shut down first (mod limitation).

Upgraded my RAM from 32 to 64, thought it might help (maybe?) with the unlimited hellfires being too much to handle. But nope, still encountered a crash yesterday after firing a number of hellfires. I do hope they fix this.

Thanks! It worked. Tested as follows... Started fresh Expansion 1.51. Used Olympus to quickly take over Oct and May FARPS with blue units. Waited for FARPS to be operational. I could then enter FARP aircraft and refuel/rearm. Waited 5mins to ensure new blue FARPS are saved. Exited Expansion. Re-Entered Expansion. Clicked on slots in Oct and May FARPS (now blue). But aircraft are blocked from entering. Waited in spectator mode for messages to complete. Selected slots again in Oct and May FARPS. Able to enter aircraft and refuel/rearm. (Previous blue units from Olympus are gone - as intended. Previous Roland and vehicles triggered by Expansion remained.) I am thinking it might have worked in v1.50 if I had followed step 5.

Not sure if George was programmed to fly that smartly. Seems all headings in the cockpit including the AI compass rose are magnetic from what I understand in the manual. Did more testing. George never holds the commanded heading and never arrives at the destination. Apache Pilot George Bearing Issue 2.trk Apache Pilot George Bearing Issue 3.trk

Hi Cfrag, please see replies below for 1.50... I will try 1.51 later on. Hope it helps.

Tried 1.50. For solo, when red zone turns blue and FARP is set up (after I send blue units into the zone via Olympus), the FARP blue aircraft are not appearing and I am unable to slot in. Is this still as intended for the time being? Or do I need to transport some troops into the zone for a proper take over that will activate the right triggers?

Have a look here... thanks. Apache Pilot George Bearing Issue.trk

To be fair, sometimes a trial is necessary not so much because it's not a good module but because you are not sure if it's your 'cup of tea'. I bought the F14 because of rave reviews. And I agree it is a very well done module. But I only flew it a couple of times and now it's been in the hangar for many months because it just wasn't for me. For that reason, I avoided the F4 although I know it is another great module. I can only say if you like helos like the Apache and Gazelle, you can't go wrong with the Kiowa.

I went ahead and installed 5.5.1. Worked fine for me. Steps I took: Unplug USB cable from PC. Install 5.5.1 (straight over 5.4.2). Reinsert USB cable. Started TrackIR software: Working. All previous settings were retained. Started DCS: Flew some helos. Working fine. Edit: I am using TrackIR 5. Might not work for TrackIR 4 since the download website says: Requires TrackIR 5 Series hardware or newer Windows 10 or newer

The NP forum said to update the games list. Did you try that? Btw, what's new with the update?

I find that at higher speeds like 70kts and above, George as pilot acknowledges the required bearing you command but never quite aligns the aircraft with the bearing. Is like he is flying a long turning arc to get to the destination.

When the FCR show targets in the NFZ (because a scan was conducted when the NFZ was not active), is it correct as is that the NTS button presses will still cycle through those targets (within the NFZ) even after the NFZ is made active? Meaning the NTS button basically cycles through whatever targets are shown in the FCR regardless. I understand that when an FCR scan is initiated, it will not show targets within an active NFZ.