MadTommy

Very happy with my X52pro.

lol yeah right. This release has brought lots of good things.. but solid is not how i would describe it. Feels very much like beta 6 to me. You must play multiplayer very differently to me. http://forums.eagle.ru/showthread.php?t=67894

This is the best thread to discuss this.. its fairly complicated, but its all covered there. EDIT: see 1st post, new fix for this added to the guide. Thanks to Kurky

It appears to me that the TAD map resolution has been reduced. Anyone else noticed this or is it my imagination? It does not look nearly as clear now. I might see if i can use the beta4 map titles.. might be my 1st mod :P

Yeah datalink in MP is knackered .. http://forums.eagle.ru/showthread.php?t=67894 Seems it might be in SP too.

Been wanting that for a long time...... no joy. Not in, FC, FC2, BS and now in A10c. There must be reason.. unless they just want to punish us mission makers! :P

^^ +1 Also it would also be nice to get the QFE before you are on the runway, maybe at start up or taxi communication.

I can confirm this all works in the final release.

After a real struggle to setup my HOTAS... The good: Love the new sounds, good optimisation (high fps), good looking lighting, TGP alignment bug fixed!!, flight feels very nice, stable etc The bad: annoying warning alarm for 1st 2 minutes of startup (but if its realistic, fair enough), HOTAS setup crashes & bugs. The ugly: Fog still looks crap from above, new radio menu (I really don't want to see this on my screen, what's the point of it?) From my 1st flight it's looking very good, Thanks ED, greeeat Sim. :)

Yeah.. i noticed that.. there seem to be other bugs too.. not sure what.. but the app has crashed/disappeared about 10 times while setting up my HOTAS.. a touch frustrating.

Good to hear..thanks.

Unstable. Not flown yet, but the application has 'disappeared' twice in 1st 5 minutes while adjusting my Options. Hopefully not indicative of the future.

No need to apologise mate. Things don't always work as we hope, especially in its beta state. If i have time i'll have a look at it in the editor and see if i can see an issue.

Thanks for sharing, just tried this, and had some issues. Jaguar 1-1 went nuts, started off ok, said he was sending data on convoy, but never did. Then started spamming Ready for 9-line Abort abort abort Ready for 9-line Abort abort abort Ready for 9-line Abort abort abort Ready for 9-line Abort abort abort Even though we never attacked. Tuned out radio... attacked the convoy that was stationary, as soon as i killed the lead tank it started moving. Decide to fly home. :cry:

Thanks for the mission. Flew this last night with a couple of mates, was fun. Not sure what the SEAD did, but there were a ton of Tunguskas about, tough one. The 2nd JTAC would not respond.. but had fun anyway.

I've got the Kindle 3.. works great on pdfs & the manual. Best if the manual is cropped.

I agree with the OP. Random failure seem pretty regular to me. Too often in MP. I do think they are a good thing, but prefer the way they are in BS, where you can set there likleyhood of occurring. I don't mind them being forced on.. but not at there present rate of occurance. I only fly MP so not sure if they are more common in MP mode, but if folks have not noticed them i would not be surprised as i see them frequently.

Understood. That problem on my mission with the road block was actually an error on an early version and has since been corrected. I did test the above system with no issues. But i'll keep an eye on it.

Thanks.. from both your inputs i've found an even simpler way that works. Just two triggers. Message is repeated every x seconds :)

Ok, here i'm sharing a mission framework I've created. This will always be 'work in progress'. If i wait for it not to be to share, it'll never be shared. ;) This is not for the uninitiated mission maker, this is in fact pretty complicated. To be honest, i expect it to be a little daunting to the majority as you have not built up the trigger system from scratch, please ask any questions you may have. Main Goal: This structure allows you to make a mission that can be played over and over again, and you won't know what the next task is or where the potential threats are. With 256 variations this should work well. The mission should also always be balanced, as there are NO random triggers, you can control the mission precisely. Explanation: (excuse me if this is a little long winded, it's not easy to explain) This is a template for a mission structure. To be honest it is not random, it is in fact very structured with equal odds of any one scenario be active. It will allow for a minimum of 256 different scenarios from one mission. It allows for 12 tasking, any 3 of which will be run in any one running of the mission. At the mission start there is a pool of 4 tasks, any one of these has a 1 in 4 chance of being selected. Once this task has been completed there is a another pool of 4 tasks, of which there is a 1 in 4 chance of selection. This occurs 3 times, i.e the 3 tasking per mission. There is also a system to allow for a pool of 4 mission threats & environments. There is a 1 in 4 chance of these being selected. So this gives you 1/4 x 1/4 x 1/4 x 1/4 = 256 variations. If you follow it as i intended. It can of course be used in different ways. And please alter it as you wish. The template has 1 player & 7 client slots included. So it can be a SP or MP 8 coop mission. This of course can be expanded. I have provided an excel sheet to go along with it, this should help you understand it a lot. The excel file has two sheets, one called Logic has the template trigger system written out. In order to make the mission you have to add all the taskings yourself, and all the tasking success criteria. And all the threat & environment (group activations) too. Where this is required there is red font. I have also colour coordinated trigger types to help make it easier to follow. Most of the 'message to all' are just place holders for mission creation. The second sheet, called Data, is what i use to add the missions & threats. It helps me keep track what has been placed. This is basically empty, be ready to be used with this template. It may be of no use to you. As i said if you like the look of it and have further questions post away, but at this stage i won't spend ages explaining the details of the template unless there is genuine interest in it. Its just too complicated. I hope if you are familiar with triggers & the editor and with the help of the excel file this might help you create some diverse missions. If you have any suggesting for better way of doing things i'd love to hear them. But please remember this framework is designed to work under all the betas and MP environment, so i have tried to use a fool proof trigger structure. The excel has been attached as a zip due to attachment constraints. Enjoy, feedback much appreciated. Coop8_Template_Random(256).miz Template data.zip

Thanks mate, I've never been sure about "Switched Condition", just haven't got my head around that. I also don't like using "continous" as i just imagine it to be very resource intensive. I generally just use Mission Start & Once. I need to undersatnd "Switched Condition".

hmm would this work?

I should know this or be able to work it out, considering how much i use triggers & flags, but i'm having a brain fart. Example: I want a message to play every 10 minutes as long as a flag is true (set) I know some long winded ways of doing this with 'time since flag' triggers, but it requires a trigger for every time i want the message to be played. How do i simply make a trigger loop. I think i'm missing something simple. My daft long winded way! (not showing the kill switch) :doh: (edit: this is in the wrong section, sry)

Sweet cOff thx

On each beta i've lost all my user made templates, so in anticipation of beta6 (don't laugh :music_whistling:) i thought i'd attempt to back them up. I knew there would be a file containing them somewhere, it was in fact very easy to find. \DCS A-10C Beta\Config\MissionEditor\templates-v1001.lua templates-v1001.lua contains all your custom templates. Let me know if your naming convention is different, as the -v1001 seems odd. Just for your info templates.lua found here: \DCS A-10C Beta\MissionEditor\data\scripts contains the default templates provided by ED. (all two of them)