PVT Watt.J

Well, good news: Everyone in on this forum can participate in testing as I am not terribly discriminating in the builds I post on here! Rest assured there is very in the way of playable builds that you will miss out on if you follow this thread.

As I said, standing on the shoulders of giants...

Slowly the Blackfoot is disappearing and the Comanche will take its place. By the end, it will have some meaningful distinguishing features in maneuverability and armament. I would never tease people anyone. I certainly wouldn't tease people with news that I have a couple guys working on multiple GUIs (Apache, AN-PEQ 1...) for entering PRF codes and that a beta system for remote laser designation could be live in two weeks time.

Update: Some giants were nice enough to let me stand on their shoulders. Cool stuff is coming...

From a pilot's perspective, size is a big deal and cannot be made up for by nice details that won't see from the air anyway. The smaller the map, the more aircraft are rendered pointless. Of course, it isn't all about pilots, but an absolute gigantic part of making gameplay work for aircraft is map size.

Can't seem to figure out how the effect is achieved. I don't see r2t being specified in script or in config. How is this done?

I recall hearing that the classnames have to be enumeratured in cfgpatches for things to show up in Zeus and that this is not required for showing up in the editor.

This is a known bug. It tends to happen when the player stats the mission inside the heli. It can typically be fixed by exiting the heli and getting back in. Alternately, it can typically be avoided by starting the mission outside of the heli.

With or without those minor issues, this would still be one of the best aircraft contributions to A3. I'm quite sure that a release based on the current state of the MV-22b would make a lot of people very happy (me included).

Glad to hear it works, some notes: 1. LOAL mode needs to be tuned to give a bit more time, but it works in concept. 2. LOBL mode also needs trajectory tuning, sometimes it overshoots. 3. There is a bug where if you fire the last Longbow hellfire the guidance won't work (this is because the game automtically switches the magazine to LG Hellfires and this means I can no longer use cursortarget to see what object the player was locked onto). I have a fix working for this working on my dev build.

Hi Taosenai, I like this mod quite a bit. I'm wondering, would it be possible to add more flexibility to where the map is placed? I use a triple-monitor setup and I really wish I could have the map on either the left or right monitor so that it was out of the way. Thanks, Shadow

Thanks Sonsalt

I don't think I'll ever quite understand how you guys work so fast!

Time flies when you are having fun staring at rotor tip mounted lights!

No worries, I have my own problematic code that I have had to rewrite so I know the feeling!

How about: I removed all the variables that are marked as local. What issues, if any, might you expect if a unit is carried into the trigger. Any guess as to what might happen if, for example, if a player is fully healed using the above while: a) being carried/dragged b) undergoing CPR c) other ongoing process related to XMed taking place

The lights on the rotors would be great, but I can't wait to get my hands on this either way.

Would this (if used as part of a trigger in a base area) then be sufficient for full healing of a unit and restoration to initial state:

The JDAM doesn't really fit well into BI's simple system for lock-on. LOAL Hellfires and JDAMS are similar in that you want to release the weapon before you get eyes on the target. BI's system does not work well for such weapons. I've been working on Hellfires for RWCO and ditching BI's lock-on and guidance made things a lot more flexible. Having assisted with and tested Neptune's implementation, I can certainly recommend it as a starting point for a new implementation.

As previously mentioned by another, I am experiencing a terrain bug. As soon as I log into MCC, some of the distant terrain becomes transparent and objects appear to float in mid-air. This occurs in local and dedicated server environment using the latest version of MCC. Any ideas?

To be clear, this bug does exist in multiplayer. It happens mainly when the player starts in the mission in a helicopter (this is simply rare in MP environment). Optics can be restored again by exiting the aircraft and re-entering. **EDIT** I suppose it might be possible to fix this by scripting the player to very quickly enter/exit vehicle on mission start.

Update released, see first post for new link, changelog!

Open up the config, find the comanche and go to the eventhandlers class. The file referenced for the 'fired' eventhandler is what you are looking for. It is certainly possible, but the pod is actually implemented as full auto. Hold down trigger and it fires as many as you like.

Looks amazing! Very nice detail work. The flir, refuel arm, the pain job all look great! I see the only hit point listed is hull. Are rotor and engine hit points on the to-do list?

There is no 'make it do what I want' parameter. You'd need to rewrite the script to make it do that.