dooom

make different MP lists and use those? i havent run into this issue yet - although sometimes the server will hang at 10% when I'm trying to load up a new miz.

Hey all. I havent been seeing any KOREAN ERA missions up lately so I made one for the community. Feel free to download, edit, add to, modify etc. I only ask you offer it on an unlocked server if you want to host it. ENJOY!! FORCES: REDFOR: 8x Mig 15, 4 x RUSSIAN P51D BLUEFOR: 8 x F86, 4 x P51D RED AI: 4 x Mig 15, 1 x RECON, 1 x TU22 BLUE AI: 4 x F86, 1 x RECON, 1 x B52 SITUATION: July 1, 1953 10:30 AM WE HAVE A PIG IN THE SAND AT HAMYSHKIY! TWO OPPOSING ARE FACING OFF TO CONTROL THIS PORCINE VILLAGE. ENEMY AIRCRAFT ARE FIGHTING TO CONTROL THE AIRSPACE ABOVE THE AO. FLY FROM YOUR BASE TO SUPPORT THE CAUSE!! RED TASK HOMEPLATE: MAYKOP TOWER/AI FLIGHTS: 3.95 MHz / 125 MHz Channel A ATC WAVE: 158 NDB INNER: 283 / OUTER: 583 MORSE: -_- _-_ AI FLIGHTS 817/827 & 486/496 AI P-51D RECON FAC: CALLSIGN COLT 11 ON 3.95 MHz AM TU-22 BOMBER: MISSION OBJECTIVES: 1. FLY TO HAMYSHKIY AND ASSERT AIR SUPERIORITY, 2. RECON FOR ENEMY BASE - SEEK AND DESTROY < 20% 3. PROTECT FRIENDLY ASSETS YOU MAY LAUNCH A P51 RECON FLIGHT TO ASSIST YOUR LOCATING THE ENEMY BASE AS A FAC. UPON DESTRUCTION OF ENEMY BASE, A TU-95 WILL SPAWN AND PROCEED TO ATTACK SOCHI AIRBASE. BLUE TASK HOMEPLATE: SOCHI TOWER/AI FLIGHTS: 256 MHz Channel 1 / 127 MHz Channel A NDB INNER: 761 / OUTER: 761 MORSE: - - - _ _ _ AI FLIGHTS CHEVY/DODGE AI P-51D RECON FAC: COLT 11 ON 256 MHz AM B-52 BOMBER: FORD 11 ON 256 MHz MISSION OBJECTIVES: 1. FLY TO HAMYSHKIY AND ASSERT AIR SUPERIORITY, 2. RECON FOR ENEMY BASE - SEEK AND DESTROY < 20% 3. PROTECT FRIENDLY ASSETS YOU MAY LAUNCH A P51 RECON FLIGHT TO ASSIST YOUR LOCATING THE ENEMY BASE AS A FAC. USE RADIO - F10 UPON DESTRUCTION OF ENEMY BASE, A B-52 WILL SPAWN AND PROCEED TO ATTACK MAYKOP AIRBASE. ** EDIT MISSION UPDATED OCTOBER 9TH ** KOREA OPERATION LUAU v1.5.miz

hmm i didnt think GROUP DEAD vs GROUP DEACTIVATE would have any difference on the respawn. I have a miz in 1.5 effectively demonstrating deactivation can trip a respawn. That said.. I'd love to see a DO SCRIPT that somehow includes a landed AI in its conditions so all the flag and triggers on each unit can be avoided.

hey all - i used to use MIST quite regularly to help with the respawn activities of AI flights. I note with 1.5; however, that the AI no longer despawns once they land at an AF (from no fuel or battle damage). Was the despawning i observed in 1.2 something handled by MIST or DCS inherently? That they are not despawning now means that my CONTINUOUS -> GROUP DEAD (XX) -> DO SCRIPT: mist.respawnGroup('XX', true) trigger will no longer work because they are sitting on the AF. I know I can force deactivations with traditional triggers but it is a bit laborious ... does anyone know if the lack of despawn by the AI is a feature or bug after they land?

wait - so AI cannot traverse tunnels anymore? ouch.. I'll have to edit quite a few miz me thinks

This is merely my observation as a dedicated prop head in DCS: Yeah, those of us in the DoW sqd regularly fly together tactically WVR and Sith is correct... its not easy with the pre 1.5 default visibility but it was certainly more that possible when we work together as a group. This is why our server never implemented the visibility mods seen elsewhere... I dont think our experience or expectations have been the same as others. In many respects it has been a credo of not denying ourselves the pleasure of our hobby and enjoying/ learning to leverage what we have. With practice, we became very good at keeping together and exploiting our multiple sets of eyes to dominate the field. All it required was some rally point designations and clear communication from flight lead on altitude and headings. We could always find each other to rejoin if seperated and find the enemy by using landmarks and proper bogey calls. Absolutely doable (aye...not easy) and our group has enjoyed DCS WWII simulation pre 1.5 with great satisfaction and enthusiasm. Now with 1.5 out, we are happily watching to see how the beta plays out moving forward. Things certainly feel different at the moment but if change can help the broader player find his way to me and pick a fight ... hey, I'm all for it... thats why I fly afterall. I'm in the wait and see camp for now though to see how the final implementation of the visibility works itself out. Feels like a positive direction to me though.

you'll always be a friend of DoW ct... no worries mate. :P

Suffering server stability issues at the moment.... Stay tuned

LOL - shows where my head's at... I can't believe I never thought of swapping them out for BVR to test.... "You know you have been flying DCS WWII planes too long when......"

yup - i attached a 4.0.55 test with the mentioned trigger structure and it is repeating the respawn pretty nicely. mist test.miz

i hear there is a bug where F10 can cause tehm to disappear for a client - it hasnt happened to me but squad mates have reported this.

i moved one of the scripts from mission start to a once time>5s->Do script file. Very wierd.

SO i noticed tonight that if I increment my versioning after a minor change to my new miz files that the file size gets kinda wonky... both versions are working fine when I run them but one is bloated by about 2-5x: These are VERY minor changes in the miz... anyone else notice this?

that looks to me like you need anisotropic filtering on... it prevents taht blur as the textures renders into the distance. Try it ON

yeah - i figured it out via elimination and getbyname was the problem - i have them respawning now with CONTINUOUS -> GROUP DEAD (XX) -> DO SCRIPT: mist.respawnGroup('XX', true)

has the MIST respawn script changed? CONTINUOUS-> DO SCRIPT -> if not Group.getByName('XX') then mist.respawnGroup('XX', true) end Doesnt seem to work anymore and throws errors.

yeah... I'm not going to redo any of the missions quite yet - might make a new one shortly from scratch but the others will have to wait until all the scripts have been patched and stable. We have 19 missions in the roster .... way too much work to do them more than once. :P

Thanks for the update Grimes... i get a bit confused by the naming conventions being used by MIST .... I note in post #836 that v.mist_4_0_55 can be downloaded yet in this thread: http://forums.eagle.ru/showthread.php?t=147792 you reference v53 for download which is merely named mist.lua on github. Can you clarify how you are approaching versioning so I know I have the latest running lua? AHA! - NM... i see now that there is also mist_4_0_55.lua in that same repository - sorry ... didnt see that earlier.

as per title. I load a profile from current version into beta for su33 and i crash to black screen when i hit "OK"

What about opening and resaving in the 1.5 ME? Does that work?

i use a repeating trigger that reloads teh FM file every 30 seconds or so... thats the only way i can get it to work in multiplayer.

Thnx crumpp.... That was a way cool thing to read.,l:thumbup:

I have never used that repair approach before - never even heard of it.... I just use the repair in the ED folder of the start menu

Thanks for the update!

I just noticed the sentences in your sig shadepeice.... I would argue that this has never been more true than in DCS