Steggles

See this thread for Mig-21 activation fix. It worked for me. http://forums.eagle.ru/showthread.php?t=136153

At least Polychop is filling my need (want) of a new chopper soonish. Looking forward to this module. Will be a first day buy for me too!

Where's the Hueys?? :(

Top stuff. Thanks for the replies guys. Looks like I'll stick to the kicking from aircraft, with thanks to who PM'd me the code for this.

First preference is only to prevent firing in the zone. I'll go with just the message in the zone for now and look about a different solution if it gets abused. Wanting this so the modern jets don't go easy target hunting on the early era jets / props within their zone on the map. Even the kick from aircraft would be fine, as long as it doesn't disconnect them from the server.

As the topic says, is there any way you can prevent player controlled aircraft from being able to fire any weapons when within a trigger-zone? _dist = get player position in regards to _triggerZone if _dist <= _triggerZone.radius then prevent player shooting This is the code I'm after. end

Glad you got it working. Editing the mission would have been my next suggestion, but I've never done it, so I didn't know if it would work properly afterwards. Happy flying with the Huey o7

You don't need to modify controls. Just pause your TrackIR when you want to use mouse aim on the co pilot or gunners. That's how I do it. The door gunners go on a seperate hard point. Refer to the picture that comes up. It will have the hard point numbers beside the gunners. I will post a screenshot when I finish work if you want.

S77th has changed their name. Now look for MD-SIM. The server is not up 24/7 atm thou cause of a loss of the dedicated machine.

1 - Try unchecking TrackIR aiming in the special options menu, then enable it again. It fixed that problem for me. 2 - Open cockpit doors (Right CTRL+C is default I think), use '/' to open intercom menu, Ground crew->rearm and put gunners in their seat. Edit - I think I got the correct slash. It's the one near the enter key on the keyboard. 3 - Dunno how to get around that one. Apart from zooming in I can't help you.

Sounds good. Might take a look at them all, considering the changes to each. Thanks for taking the time to give a detailed reply, and thank you to all 3 of you for your (continuing) work and RagnarDa for the initial concept and getting the ball rolling.

Is this script still getting attention? And of the 3 repo's I discovered in the last 10 or so pages in this thread, is it ciribob's, shagrat's or audax's repo thats keeping the up to date / confirmed working changes?

Thank you for the extension. Very solid, and neat piece of craftsmanship. Very satisfied with the 120mm extension and wasyl00 was nice to deal with during my enquiries. Thanks again, and keep up the good work.

Ok, so it turns out I didn't save the mission I did the other day, so the wind values I used in the editor didn't save. But it is correct that the mid layer between 10m and 2000m is nearly double. I did another run with these settings in the editor- 10m - 0 @ 10 2000m - 0 @ 10 10000m - 0 @ 15 Vs CDU measurement. 0 was on takeoff run before rotation at an airfield approx 70ft ASL. 0 - 173/15 500ft - 173/36 1000ft - 173/40 2k - 173/41 4k - 173/25 6k - 173/19 10k - 173/19

I've got screenshots of the CDU at the altitudes I said in that post. When I finish work I will look at the settings I put in the editor and post them along with the values I got from the CDU at each altitude. Edit: And yes it doesn't seem logical that it doubles and then reduces to the 2000m if this is the case. I will check tonight also, with 10m and 2000m at the same speed and post the same altitude / speed results from that too.

Just a few days ago, I did a quick mission up as I was doing a similar write up for my squad, and I used only the CDU values to enter the wind layers into LASTE. I had a 90 degree shift in wind from 10m to 2000m and another 90 degree shift from 2000 to 10000m. I ended up putting layers into the CDU for 0 (ground level), 1k, 2k, 4k, 6k, and 10k feet. Using values shown on the CDU, the CCIP solution for a pair of Mk-82's was dead accurate from a release 7k feet AGL. As far as I'm concerned, values in the CDU are correct when in a mission.

http://forums.eagle.ru/showthread.php?t=119503 Check this thread. His file has all the frequencies plus a lot of other stuff that I find handy for the Huey.

Chaff is implemented now? I missed that and will check when I get home. Unless I'm reading it wrong, the above post is slightly incorrect. Flares in the Huey are released 2 at a time and has 2 flare cartridges that can hold 30 flares each. The rotating knob and number displayed on the CM panel is how many flares remaining, and you have to set how many flares you have loaded when commencing a mission. Because the Huey releases 2 flares at a time (one from each cartridge) you can only select up to 30 in the window (one cartridge holds 30). So, if you've loaded 60 flares, select 30. If you only have 30 flares loaded, select 15. More information can be found on page 106 of the current flight manual, located in the docs folder of the Huey install.

There is a sticky thread in the mig subforum. http://forums.eagle.ru/showthread.php?t=136153

Glad I read this thread. Finally be able to use the co-pilot for gunning without having to hold the cyclic with my left hand :-/

I too would like to sign up as a lone wolf for Blue Flag. Callsign: Steggles Preferred Aircraft: A10C, UH-1H. Looks like fun, and will be my first involvement in anything like this.

Use the file explorer to go to your DCS: W folder. I'm not sure what start menu differences there were for me between 7 and 10. I hardly use it for anything apart from opening generic apps, and search.

Great program. Thanks. When I to Kneeboard Settings->Size and Position, a windows dialog pops up saying this Kneeboard Builder has stopped working. Everything else seems to be ok. Running Windows10.

I've been putting off this download, maybe I should get it done. I'll get back to you loaded dice, if it effects my trackIR. Edit: TrackIR seems to be working fine still.

Well in my opinion, windows 10 is great! I've seen a noticeable difference in the opening and running of applications from windows 7. My TM worthog stick and throttles work fine, and drivers were no worries, along with trackIR and my rudder pedals. Before you start putting the blame on Microsoft, try starting with the manufacturer of the X52 for having a driver and software that isn't compatible with windows 10. So far I've had Windows 10 since 2 days after its release date, and I must say, I'm very happy with the upgrade from windows 7, and I have no complaints at all apart from Edge, but after IE, I didn't expect much from that.