Wrench

If you want to invert the gun's elevation control, try inverting the mouse look bind. The gun's POA is normally slaved to your LOS, expect when TrackIR gun in turned off, so I imagine the mouselook bind is controlling the gun that way. If you invert mouselook it'll probably do what you want, without effecting your camera control since that's TIR.

RE taking on SAMs in the hog, I think it's pretty fun to use the RWR method to find a SAM whose exact position you don't know. You can fly on two bearings ~90° apart, and create overhead markpoints when the threat crosses your 3/9 line. Then use the OFFSET function to create a markpoint 90° offset from each of your overhead points. Then you create a flightplan to connect up the 4 points to make an 'X' and the SAM will be where the lines cross. If that explanation isn't clear there's a pretty good video somebody did a few years back that goes over it in detail. It's a pretty fun challenge, and gives you an idea of the kind of stuff you can do with the avionics in the hog if you have a think about how to use them. Here's the video

I use dominant eye only, (right eye.) I assume the scorpion in right eye only, meaning that if you're a left-eye-dominant A-10 driver you'd better get used to having a headache for a few weeks. I know guys who fly DCS who use both eyes for medical reasons, so use it however it makes you comfortable.

For the time being, until we get the DTC update, There is the 'Prepare Mission' function. This is in the ME when you go to the 'Fly' drop down menu. A lot of people don't know that this allows you to preset your aircraft. If you start a mission in Prepare mode, any avionics settings you change will be saved in the mission file on exit. So in this way, you can make a flightplan in the ME that has all the waypoints you want to have, then go to prepare mission and delete that FP, but use all those tasty waypoints to bid your own FPs. This will also save added WPs if you need more than 30, so you might consider just writing down the MGRS of all the WPs you want and adding them manually in the CDU. The good news is you only have to do this once.

How do you call net code from a mission? I don't think I've ever seen that done without use of the API.

Thanks toutenglisse. I still had to modify MiST itself to work with Liveries on ground units, as it's disabled by default, but at least I got it working.

I just use the old template and delete the panel. It's not too hard to find. Other then that they're the same.

There is a probability control at the top of every group's panel in the mission editor. The other option would be a reasonably straightforward script to pick random things to spawn from a list. But if you're not into scripting, the probability control should work. I don't think the probability control exists for static objects, but you can set a group to TAKEOFF FROM RAMP and check the UNCONTROLLED box in the group properties. Same deal.

If you're going the script route, add a trigger with the type ONCE and TIME MORE THAN 1 second. Then the action is DO SCRIPT, and you just copy and paste that script (or a modified version for whatever you want to do) in the text box. If you want to trigger a sound file, you can do that via scripting, or using the Trigger only method outlined above, you can just add the SOUND TO COALITION action.

I would 100% encourage you to script this. I like using MiST for respawning units, and it's really easy. You can even use mist.teleportInZone to have them spawn in a random point in your trigger zone. The possibilities this opens are endless. I regularly write little scripts like this, and have MiST assign a randomized route to the group that it spawns. The MiST documentation on hoggit wiki is really good https://wiki.hoggitworld.com/view/Mission_Scripting_Tools_Documentation and so is there standard DCS wiki https://wiki.hoggitworld.com/view/Category:Scripting But for your purposes, the script would consist of one line. mist.respawnGroup("redAir" , true)

You can add submenus via script, but you still can't load a mission from those. I'll second this should be in Mission scripting.

This is a bit of a necro post, but I hate when nobody answers my questions. I use MiST for logging, since it can serialize tables and drop them straight in the log. So you'll load up mist before your script, then at the top of your script run something like GizmokevLog = mist.Logger:new("Gizmokev") Then whatever you need to log, you can do so like this: GizmoevLog:msg(MarkerCoord) This scales, so you could even log EventData if you want to look at the whole thing. I've done stuff like this before, and I use S_EVENT_MARK REMOVE (id 27) because otherwise it may try to run your code as you type. This way, you type what you have to type, then delete the marker. If you need the marker to stay there, it's a pretty simple task to have the script re add it. I also use something like if string.match(event.text, "-do") then --runs some stuff end That way, you can start your marker text with a key word to differentiate it from other types of marks, or write several functions which you can pick between. In this case, it would look for the text "-do". Also remember you have to run addEventHandler after you set this all up. I'm sure you did, but it wasn't in OP so I thought I should mention it. Let me know if you need an example, I've got plenty of them, just not on this PC.

Have you thought about spawning them with script? You can use MiST (or moose, but I don't use it much myself) to define a zone, then get a number of random points in that zone, then spawn a cow at each point.

I'm using mist.cloneGroup to clone ground units, to whom I've applied a custom skin. They are spawning with the default skin, which does not fit the mission I'm building. Does anyone know a work around? The mission originally had them using the default skins, so I've tried creating copies of the groups in the ME, then deleting the originals, then renaming their replacements to the same naming conventions, but to no avail. I also tried making a new test .miz, and same results.

This isn't working for me, I assume it has to do with the new forum. Any chance of a new link?

Kind of a late reply, but if you're the one making hte mission, have them broadcast on some frequency. The FM radio can do homing with the small needles under the HSI, for AM freqs you can use the AM ADF radio, which will give you pointers on the HSI.

I'm really happy to see this mod is back and working!

My vVF is still having this issue. Any chance of a development report?

The NVIS lights are unmodeled, same as the old A-10C. I'm not sure why. I heard that it was something ED was told not to include in the civilian version of the sim from years back, but so wat the HMCS so I'm not sure if that's still the case.

That depends on what you mean by "simple." It should certainly be possible with ultraMFCD, but it will take a little setting up. I'm not sure how to get it to only display in the alt-f1 view, but I imagine it's possible. (maybe setting alt-f1 as some kind of toggle hotkey in ultramfcd?) I don't use it myself since I fly VR, but there are plenty of forum members very knowledgable on the subject that should be able to help you out.

Does changing the normalmaps for otbher things I saw terrais mentioned above) pass IC? Ifso,I might feel a modpack coming on.

I'll throw my two cents in and say that if that's how the real plane works I'm all for it. I'm not particularly against having it as an option, but it'll sit unused in my personal settings menu.

I second that we should have a one eye setting. I'm fully prepared to assume that ED always planned on adding it in, so I'm happy to wait a bit for that to come down the pipeline. As for Foka's assertion: While I'm certain that the source you reference is accurate, I can only assume that that's one pilot's issues and not something that would affect everyone. I've used the JHMCS a lot, in one eye only since launch, and never had an issue. I gave it a shot in both eyes just to see if it made a difference for me and it really didn't. Just like with everything else, every person is an individual and will have different reactions to the same stimulus. I fully support having a 'both eyes' option for those who need it, but for at least some of us, it isn't necessary at all.

It depends on the mission. Many missions include them, and the information will be in the briefing. You'll have to tune the appropriate radio to the frequency listed in the briefing, and then find "JTAC" in the radio command list. This is typically the 4th option IIRC. You can google "9-line CAS briefing" to find some helpful documents on what he's saying actually means. If you're creating your own mission, place a ground unit and give them a FAC waypoint task. There are a few options and it's best to just explore them a bit.

Seconded. I've spent some time lurking through the scripts folders, and haven't seen any references to the HMCS profiles. The CMS programs from the old A-10C work though, so I'm hoping that something like this will be added/found.