ENO

Not seeing pitot heat in either of those. Most say irl to turn it on after takeoff since it can overheat but more often than not (in the sim) it gets forgotten and causes other problems. Overheating the pitot isn't modeled so why not just hit it when you hit the o2?

Not sure about that- worked fine for me. new.miz

Beo- my comment wasn't really pointed at you specifically as much as just commenting on how others get pretty excited when things don't work and in their absence it doesn't mean there isn't still a problem ;) Anyway- Turning things off now may be slamming the gate after the horse runs out... it MAY work- but you might want to add one more step to it to be sure. In reviewing the issue with Bit Defender, it looked like it was blocking some files during the install / update process so you may have missing files. Of course, if you tried to repair or reinstall or rename- while BD was still on- it's probably still just blocking the same files. So on a two pronged assault... do as Kontiuka says... turn off BD, cycle your computer (with BD staying off), THEN run a repair. Before you repair you may consider possibly renaming the saved games / DCS folder to DCS1. Repair and check again. Once it's installed and working properly we can try working BD back into the mix.

UAC off is a new one. Thanks Sam.

All good army- DCSW is the base and is free- gives you that training P51 and the SU25T. All the other modules like you have mentioned (FC3, BS2 etc) are added to DCSW. There are a few aircraft coming out individually now (F-15C with AFM, SU25) that are all included in FC3... does that help?

http://forums.eagle.ru/showthread.php?t=120836&highlight=triggered+actions Described there... unfortunately I see my screenshot is kaput since I junked photobucket. Basically, the icon you need is right next to the weapons loadout screen in your unit menu. Looks like a square thing with squigly lines on the corner- you'll see it- just to the right of the missile looking icon where you configure unit liveries and loadouts... fuel etc. That's called "triggered" actions. Once you're in there you have the same kind of "advanced waypoint" options menus available. You can set these up for deployment in your trigger system. Don't make the trigger occur at mission start since I don't think that's been working. Instead... do a "run once" trigger with a time more (10) condition and then do AI TASK PUSH. You can then go find the appropriate task for the unit you selected. Let me know if that works? Kind of curious as well.

I reported similar behavior quite awhile ago and I'm surprised to see it again... Have you tried to "trigger action" / ie: force the action yet? I didn't know how to do that back in the day but it's quite easy. I won't bother explaining it if you've already done it. If not, I can walk you through it. http://forums.eagle.ru/showthread.php?t=104918&highlight=ships+hold+fire As you'll see I got no response there...

Just initiate MIST or do it without condition at "mission start"- do script file as is. Make sure it's v3.4. You can then use the MIST guide to go find and edit the part that you need. Also recommend the wiki here: http://wiki.hoggit.us/view/Units_in_zones I think default CTTS load is 11-12... so if you said minimum number 10 (you know, in case you lose any along the way). You could also toggle it so that the flag turns off when your number drops below the minimum.

Well- mine is working fine... so let's see what I have: In my saved game / dcs / Scripts folder I have an export.lua and a TacviewExportDCS.lua. Do you have those in place? Also, any chance at all that Tacview is monitoring an unused beta version? I've seen that kind of thing happen before...

I'd be inclined to either just run a repair or go into the DCS World / MissionEditor folder and rename modules to modules1 THEN repair... and try that.

Your awesomeness knows no boundaries! thanks Ajax.

Problem signature: Problem Event Name: APPCRASH Application Name: DCS.exe Application Version: 1.2.8.27915 Application Timestamp: 537df6ef Fault Module Name: edCore.dll Fault Module Version: 1.2.8.27915 Fault Module Timestamp: 537480e5 Exception Code: c0000005 Exception Offset: 000000000000286a OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 4105 Additional Information 1: e17c Additional Information 2: e17c54aa3775ceab26b71c8ff00e8f1a Additional Information 3: 4738 Additional Information 4: 4738413ef64ff936f6c9214e3bb94f13 From your log... 08146.011 INFO NET: Reconnecting to master... 08505.575 WARNING LOG: 1 duplicate message(s) skipped. 08505.575 INFO TERRAIN: lObjectFire::lObjectFire for building id=279380 08757.081 INFO NET: Reconnecting to master... 09621.024 INFO TERRAIN: lObjectFire::lObjectFire for building id=279134 09966.399 WARNING LOG: 1 duplicate message(s) skipped. 09966.399 INFO NET: Reconnecting to master... ^ that was the last entry before you crashed (apparently)... so it seemed connected. crash 07.01.14.zip

Posted your comment at Simhq Mav and this is what we drummed up. I'm not sure about on the firehouse- I haven't been paying too much attention to it. I'm going to look into it now though.

There are quite a few people experiencing outages, actually- just because they're not all jumping up and down burning the world to the ground doesn't mean anything.

Anything like this in your logs? 08146.011 INFO NET: Reconnecting to master... 08505.575 WARNING LOG: 1 duplicate message(s) skipped. 08505.575 INFO TERRAIN: lObjectFire::lObjectFire for building id=279380 08757.081 INFO NET: Reconnecting to master... 09621.024 INFO TERRAIN: lObjectFire::lObjectFire for building id=279134 09966.399 WARNING LOG: 1 duplicate message(s) skipped. 09966.399 INFO NET: Reconnecting to master... In particular the "NET:Reconnecting to master" entries...

^ Love that helicopter script by the way... I found it somewhere but never knew who made it. using the group / unit in zone MIST function may also work though I believe they still call infantry a ground unit. I like that since it allows you to state the number of units that need to be in position to "hold" the objective. It also has a toggle / stop feature that comes in handy. It's also removes the need to identify exactly which group needs to be in the zone- and accounts for ANY ground unit. Just pick a required number that fits the number of infantry in your group...

I hadn't thought of it before but used in tandem with MIST destroyed map objects in zones you could probably jury rig something in the interim. Basically pick your depot area and if it gets destroyed (or a building in a zone around it gets destroyed) you can "plant" an enemy soldier somewhere- which ends up preventing airports from providing services. At least in theory that would work but yes I agree would be a lot easier if these functions were built in.

I think someone has already done that but it probably wouldn't hurt to do one with 128. Looking forward to the results.

Your internet connection drop near the end there I wonder? Suddenly it just started trying to reconnect...

And you have DCS world enabled on the taview side?

Yes I've been anxious to do some scud hunt (style) missions. Ground commander would need to hit certain targets in a certain amount of time and air forces need to destroy his assets before it happens.

Last update as in 127-128 or one of the mini updates? Did you redo your controls with 128?

Yeah- that's awesome if my wingie is another A-10C

I think in practice in the sim the only thing that works is either lots of chaff or lots of flares- so manual is the best way (IMO). You need to know how to set your own programs, however- and once I learned to do that then it was simple. Just right click on the CMS panel switch on the far right hand side- and you'll see the current program settings. Then just click the one you want to change (the square button underneath that item) and then use the rocker on the right hand side to increase or decrease. Choose your quantity, and time, and cycles... done. My A program is basically just a friendly single flare (in the event my wingie loses me)- B program is uber flare and C is uber chaff- 4 bundle .25 second interval for 20+). If I can see the missile has been decoyed then I just stop the program. I used to have a different setup for preventative flaring but I think it's generally agreed that it doesn't work anyway so I moved away from it. Semi isn't bad but it still doesn't quite cut it- again only my opinion.

Therein lies your problem. Needs to be 64bit OS... it's no longer compatible / supports 32bit OS.