dooom

:shocking: at 1:35.....

I had this bug a few years back... What is your card and are drivers up to date?

Hmmm. Might be a bug with new update then....?

Happy holidays gang!

NOTE** I was able to resave all the missions and restart the server while the wife was wrapping presents. please advise if you still see the anomolies.

WHAT?!?!? very odd. We may have to open and re-save all the missions on the server since there was a new update - maybe it farkled something up. My apologies however, it is xmas eve so i will not be able to looka t this for a few days.

... kills may be harder ... but damn... they are sure sweeter :) Congratulations on the First A2A kill!!!

yeah - im pretty sure this is correct... as far as i know if an enemy is over a friendly ground troop with fog of war or engaged with a friendly fighter, then it is "reported" on F10. thus if you are in enemy territory your likelyhood of being exposed on f10 while your opponent is not is fairly high. as for the use of flak - i agree its not ideal but we try to use is strategically and publish "flak maps" with most missions. thus you can typically fly a barcap/ingress/egress unexposed by the bursts while looking for your prey to trigger it. I personally recommend folks study the flak maps when they are available and try to use map landmarks to navigate without triggering it.

how is your trim? the 51 will bleed E if not trimmed up. do you have yaw askew with your rudders?

I'm happy to report the miz is working as intended! Quick question however... I note that once the war goes "hot"... There is a quick escalation of ai spawning to a point where the ai is flying across the border leaving original cap zones vacant to attack opfor behind lines... Is there anywhere I can try to reduce the # ai spawning in a hot situation??? Should I just increase tasking interval?

check out the dogs of war server... that should be in the tail end of our busy period.

checking the edits tonight! thanks for the insight.... it looks like it may have been a "cant see a forest through the trees" sort of thing... Cheers,

look for me on the DoW teamspeak... im usually making missions and always happy to screenshare via teamviewer to teach a bit.

thanks stone, i have the GCI msg commented out because it was interfering with the trigger messages... I also am using the awacs script for gathering BRA by ajax... noborders=0 ... ill test the interval at 600 and see what happens I messed with it a bit more tonight and observed some strange behavior with the initial cap spawns... sometimes it will spawn 4 red flights and no blue, sometimes it will spawn 4 blue and one red... vrey inconsistent. Is it tied to when clients enter/spawn ? I can't seem to get a consistent presentation of AI flights and am wondering if i am missing something. I'll fire you the latest miz by PM again. Thanks Stone... i really wish i could give you more rep. Cheers,

i'll pm you a dropbox link to the miz... its pretty big - only look at it if you want to though... I really don't want to inconvenience you or snafu - its a busy time of year. I am not sure how to check if the GCI is actually assigning contacts or not. A couple of questions though... - im not sure i follow what you mean by border "active"? perhaps im missing something? - AI flights are set to excellent. Patriot STR sites are set to excellent. - tasking interval is at 300 - maybe I should raise this? my edits to the script are attached below. the .miz will be pm'd as a dropbox link if you are interested to look. GCICAP20141017DoW1.lua

heya stone, i made the changes above in post 329 but unfortunately the CAP and GCI are not intercepting, I got within 18nm of them and they just turned away... is there anythign i am missing to try and ramp up the aggressiveness?

very cool - i'll have a peek at this. Very much appreciated

If a radio is not tuned then canopy has to be open... If it is tuned then you should be able to call with it shut . I believe all the miz I have made have the radios tuned but I know there may be a few without that I did not make.

Do you have your controls indicator on? Is it possible you are trying to trim beyond the limits of control throw?

That would require the radio add with a script though . How would you trigger it, am I missing something?

Sorry I haven't helped you test yet ... I have been head down finishing a few new miz for DoW. I hope to look at this one soon!

You are a great supporter snowtiger! Thanks for the kind words :)

109s are in Frog of War and LooseLips. We have them added in our beta set which we will be releasing soon to bring our miz count up to 12. Its a big update to the rotation and we will probably announce it in the multiplayer forum when we do it. Just waiting on a couple of skins to get finished and included in our skin pack and then I'll push them live.

works like a charm! thanks ajax!!!!!!

Hey all - i am finishing my touches on a longitudinal mission that has quite a few long distance targets for the WWII set. Each side has 7 objectives they can pursue. That said, it dawned on me that i need some sort of reference to allow a client to know which of the objectives have been completed so they dont spend an hour flying to a target to only find out it has been destroyed. So far both sides have the AWACS script by ajax and a Radio ITEM add based off CTTS loading at the start. these items are working and presenting appropriately to their respective coalitions or groups. I thought I could use the radio item add for coalition trigger to create a list of objectives taht are then removed via radio item remove for coalition once the objective is completed. Unfortunately, these triggers overwrite the AWACS/RADIO add script insertions rendering them unavailable... i also note that the coalition lists are not appropriately showing to the proper sides... blue gets red and red gets red. Any suggestions from other miz makers on how i might handle this problem? I am 99% done the miz but dont want the user experience to suck if they fly across the AO to a completed objective. Help?:joystick: