fargo007

Hahaha! I love the criminal lineup of the three insurgent guys.

Preach. So easy to delete the wrong thing and then have to reload and lose all the work since the last load.

I have a modified version of it working where if over land it spawns the soldier, and over sea it spawns the life raft (a mod). The call for determining landtypes in multiplayer isn't returning in a completely reliable way so I am still testing. It seems to consider a good portion of coastline to still be water for some reason. Once I neaten it up I will contribute the code if Ciribob is interested in merging it. Essentially it would let you parameterize your wet and dry objects.

Exactly as title indicates. Turn labels off in the mission (enforce is checked, on/off box is not), start the mission and join the server and labels will be on/available. The enforcement actions are not working in MP.

Left Shift & F9. But I think there's a bug with labels now. They are enabling all by themselves in multiplayer, even when specifically disabled in the mission (enforce is checked, on/off is unchecked).

I'd REALLY like to see the dedicated server run on Linux. This would really open up new possibilities.

Where's v1.2? I only see 1.0 and 1.1 in the initial post.

Thanks for trying to help. I'm using 1.1 here. On OB, latest version. I have the folder "Desert Farp -By Suntsag" in my OvGME mods directory. It activates fine. It gets installed in \Saved Games\DCS, such that I see these folders there: \Saved Games\DCS\Bazar \Saved Games\DCS\Bazar\Textures \Saved Games\DCS\Bazar\World with their contents the same as in the mods directory. I've reinstalled it a few times. All I have available is the regular FARP, which lately looks like it's snow covered. /Fargo

It seems that in the latest version, these lines are different now, and none are commented out: --Night Vision Goggles {combos = {{key = 'H', reformers = {'RShift'}}}, down = device_commands.Button_5, up = device_commands.Button_5, cockpit_device_id = devices.HEAD_WRAPPER, value_down = 1, value_up = 0, name = _('SA342 Night Vision Goggles On/Off'), category = _('Night Vision Goggles')}, {combos = {{key = 'H', reformers = {'RShift','RCtrl'}}}, down = iCommandPlane_Helmet_Brightess_Up , name = _('Night Vision Goggles Gain Up') , category = _('Night Vision Goggles')}, {combos = {{key = 'H', reformers = {'RShift','RAlt'}}} , down = iCommandPlane_Helmet_Brightess_Down, name = _('Night Vision Goggles Gain Down'), category = _('Night Vision Goggles')}, Yet the NVG's for the L and the Mistral are nonfunctional in the current version as of today. Anyone wrestle this down yet? /Fargo

I'd buy it, as soon as it was offered.

Doesn't seem to work for me. I'm seeing this in the logs: 2018-09-02 15:05:18.686 ERROR EDCORE: Cant open file: /models/farps.lods.json. 2018-09-02 15:05:19.035 ERROR SECURITYCONTROL: Manifest hash check failed for file 'textures/farp_n_2048' 2018-09-02 15:05:19.058 ERROR SECURITYCONTROL: Manifest hash check failed for file 'textures/farp_spec_2048' 2018-09-02 15:05:56.651 ERROR SECURITYCONTROL: Manifest hash check failed for file 'textures/farp_2048' The mod activates via OVGME just fine. I have mods installing under saved games. Does this one need to go in the main DCS install? What to check?

Make sure you are not turning the show models feature on in the ME.

Based on robgraham's ID of the fault, I went into the settings.lua in saved games/Mission Editor, set ShowModels to false, and was able to substantially modify a mission without crashing. More testing, but promising. ETA - I also deleted some old track files in there, not sure that it matters. Full half hour of editing with no crashes thus far. 1+ hours... Zillions of changes.... Yup - this is the fix. Back to serious designing work!

Came here to report this. Seems to happen mostly when in the triggers menu.

Thanxbro! We appreciate what you creators do a LOT.

I can't find that anyone's ever done a replica of the OBL compound. It would certainly be useful for a conjectural mission.

Bump. This is still going on, and I would like to call it to someone's attention. A key part of the Persian Gulf map deals with shipping and maritime operations. This is a huge mission blocker. Can someone help please? Let me know what other information to provide. Thanks!

The pop up never worked but now, even with "NS 430 ALLOW" checked, the unit is not there. Is this known issue already?

I'd recommend two different types of missions for learning how to shoot approaches in the Mi-8. 1 - DLQ. Set two ships up parallel to each other, about a half mile apart on the same heading. Go back and forth landing correctly (come to hover on the left side, slip right and land). 2 - CSAR missions. Set a mission up with the CSAR script and have a bunch of planes over top of a huge bunch of red SAMs. Remove the SAMs after a certain time. Enough time to let them shoot the planes down. Going around and picking up the pilots gave me a really good understanding of how approaches need to be planned and executed, and especially how you need to handle power as you come out of ETL.

I just got some help here, so I'll try and pass that forward. It seems what you want to do is define a set of clients, and then perform a set of operations per client, where right now it's locked into a singleton model. The SET class does this, specifically SET_CLIENT. You define a filterprefix that includes the clients (by name, e.g.) and then you get a callback function for each matched client that you can use to accomplish what you are after. https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Set.html##(SET_CLIENT).ForEachClient Download the MOOSE example missions. There are some examples of this being used in there.

Thank you guys! land.getSurfaceType() returned exactly what I needed. I love this place.

Just wondering if there's a way to determine if a point is either feet wet or feet dry. Thanks, /F

Go to youtube and start going over some of the howto's and tutorials. Lots of good stuff there.

Preach. This is some amazing stuff. I'm trying out suppression right now.

Had the same problem. I deleted my FXO and metashaders and let them regenerate and this fixed the issue for me. I do this every update now.