FubarBundy

Hi, is anybody else having trouble getting AI ground units to behave themselves. I'm finding that they are reversing from their positions, getting stuck on slopes and going round in circles when they are supposed to be advancing along a road. These are units placed and active at mission start btw.

THanks Grimes, yes that makes sense.. it does seem to be a bug. Hopefully fixed soon but makes mission building a bit of a pain presently.

I've been playing with JTAC etc.. recently. It seems that the recon group has be quite close to be able to mark with laser regardless of unit type. So much so that I'm pretty sure they would be spotted and killed very quickly irl. That being said however, I've managed to get all kinds of things to lase, even armed houses etc.

Hi Grimes, The problem is with the Recon group. They open fire as soon as spawned, (despite being set to "hold fire". They are also visible to the enemy despite being set to invisible. Also, they seem to want to reverse very slowly away from their spawn position. CV1copy.miz

Anybody else having trouble getting units not to open fire using ROE hold fire or setting options to "invisible" ?

VERY useful! Really, really useful Sven... should make using Moose a doddle :)

Thanks FC... much appreciated :)

When fiddling around with LUA scripts I've been getting the following error on trying to restart the game... WorldGeneral.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc0000020. It goes away after a repair but happens again after making script changes from within LUA Development Tools. Anybody have an idea on what is happening and how to prevent it?

Weather and Vikhrs I've found that weather can sometimes have a nasty effect on Vikhrs... particulary strong winds. It can cause them to "warble and hit the ground". It only seems to affect the missiles loaded on one side of the helicopter though.

Would this do what you need? https://forums.eagle.ru/showthread.php?p=2514900#post2514900

Hi Sithspawn, well at least that is some feedback so thank you. Like I said though, in and of themselves, the bugs aren't so much the issue... its the, (at least as it seems to me), lack of support and guidance for people working with the mission editor. And yes, we all do have things we want fixing but surely the mission editor is a priority for the sim as a whole and should be prioritised.. at least in terms of giving info about what does and doesn't work and any workarounds known to the ED team themselves? Please understand that none of this is being said out of animosity... actually quite the reverse. We are all huge DCS fans who just want to make our flying environment as good as we can. Again though, thanks for the feedback.

Hi all, This is, in some part, a reaction to FlightControl's decision to stop work on the wonderful Moose project and, in some part, a rant that's been a long time coming. I have been running a server, (CoffinDodger) for some time now but it is presently down. Initially this was due to a hardware failure but it has stayed down because of the time it takes to find workarounds and fixes for long known bugs and problems within the scripting engine. I have posted along these lines before but will state it again... DCS, no matter how fantastic the flight models and no matter how beautiful the aircraft models etc.. would be pretty much meaningless without the scenarios created by the mission making community. I am no programmer but, thanks the the likes of FlightControl, Grimes, Ciribob et al and the frameworks and scripts they have created, even I have been able to produce some pretty decent missions which, (connection issues aside), have proved to be quite popular at times. In truth, FlightControl's decision to leave the Moose project involves personal reasons but there is also a deep frustration with the way ED interacts with the mission building community. This is not surprising as the interaction is little to none!. There are mission editor bugs which have been around for months, (if not years) and these cause all mission builders to tear their hair out regularly trying to find workarounds and fixes for things that just don't work as they should in the first place. We all understand that any piece of software as big in scope as DCS will always have bugs and problems but it is the lack of communication, feedback and assistance from ED which is the problem. I find this bizarre as I see mission design as fully 50% of DCS and, from where I'm standing, this 50% of DCS seems to be woefully under supported and under valued by ED. Every week we get a newsletter telling us about the latest bundle offer or modules in development etc.. (not knocking that because its a good thing), but could ED not also put up news regarding features and plans for the scripting engine?. Could ED staff and or 3rd party developers not post their own tips and pointers regarding how to get the most out of the mission editor or even have somebody respond to queries and maybe even give out little snippets of code in response to feature requests? Please understand, I am not knocking DCS or ED but I am puzzled as to why the mission builders and server hosts get so little support and attention. I strongly believe this should change because DCS has the potential to be something truly amazing. People like FlightCcontrol are an asset of untold value and should be recognised as such, not driven away by frustration. Anyway, rant over. Hope somebody from ED reads this and understands what I'm getting at.

sorry to hear that m8 Hi Sven, Really sorry to hear that but completely understand. Between work and loved ones its hard enough to get decent gaming time... let alone a project the size and scope of this! Secretly hoping you will take a break and then your addiction will get you again.. (hopefully not to the same extent though maybe) Anyway, thanks for all the help and what is a fantastic framework... even if it isn't quite complete yet. Good on you m8, hopefully speak u soon

CTLD not working for aircraft in same group CTLD does not seem to work correctly for aircraft in the same group. Although all aircraft get the menus, they only work for the lead aircraft of the group. Is there any work around for this ,(other than having all client escort heli's as a separate group), or is it to do with the group bug in the mission scripting engine? Disregard, just found a post from 1 year ago regarding the same thing. Separate client groups it is then :)

ME bugs +1 Mission editor bugs are off putting for mission designers. It's so time consuming to track down and make work arounds for bugs and inconsistencies which prevent things working the way they should. Mission design is a major component of DCS. Without the ability to design missions effectively, DCS is meaningless regardless of how great the aircraft and environment are. Please, please please fix the bugs so we can get to work on the missions this amazing simulator should be more than capable of running.

May have already been reported... FARP atc doesn't recognize when helicopter has taken off. Radio menu stays at "abort takeoff". Therefore unable to ask for nav assistance, request landing etc...

Nice :)

same for me. no option to install in module manager

Thanks for the quick reply Grimes. Seems sorted now, the log reported that it was unable to access the missionscripting.lua which was in read only mode for some reason. Unchecked it and seems to be working now. Thans again :)

error with slmod Hi. can anybody shed some light on the following error when attempting to use SLMod on server machine? (using MiST and CTLD) --------------------------- Mission script error --------------------------- [string "slmod.sendData()"]:1: attempt to index global 'slmod' (a nil value) stack traceback: [C]: ? [string "slmod.sendData()"]:1: in main chunk --------------------------- OK --------------------------- thanks in advance :)

I would like either some way of using my copy of NTTR on a host machine simultaneously with a client machine or a free "server only version". Seems a bit much to ask those of us running dedicated servers to pay twice in order to benefit the MP testing / community in general QED.:noexpression:

nice :)... glad to help

I've found this problem too. The work around for me was to make sure the "unit in zone" condition is used as opposed to the "group in zone". Hope this helps.

Not sure about the first examples but in Magistral, you have to be near the the group of infantry you want to pick up.

Nice work m8.. that seems to have helped a lot. Still get the micro stutter on occasion but that seems as much related to head tracking as anything else