ENO

I've always just made a mission start trigger with no condition and opened it in a do script file action. Some people run once / time more 5-8 seconds / do script file. Either way any mist dependent scripts needs to be loaded a few seconds (I do mine with time more 10) after mist-

Hmmm. You said on vista- what are your system specs?

Thanks DAvis... I see just about all of them are named differently than what I used. I'll try that and report back. (Tried to rep but no joy.)

My longest running is an Intel... Samsung is my new favourite (just about everything I run now is samsung at any level... SSD, washer-dryer, monitors, TV, blue ray... etc). What can I say- they build a good product.

If you've updated drivers, then rename saved games / dcs folder to "dcs1" and let the game recreate it in its entirety. See what happens.

try going into your user / saved games / dcs folder and rename it to dcs1... let the game recreate it. See if that helps. If it does, then you can move your input folders etc over from the old one to the new one. Might have to re-enter a few settings

There have been intermittent outages / incidents like this- in most cases short term and they resolve themselves. There are a couple network related files in config- frankly my first step is to rename the whole folder in saved games to dcs1 then restart the game. Though you're right... Most issues are resolved with just that one file... There's also a vault file and I'm not sure what role it plays. Figure maybe your ip got changed after not being used for awhile. Can you post a log? Maybe we can see a little more under the hood.

Hmmm- I think there are a couple things at play here... mixing up laser and GPS guided weapons. You shouldn't need to use laser for the 38s (though some people do use it to set an accurate SPI- you don't NEED to use laser to do so) and it certainly won't prohibit you from dropping. If your GPS wasn't in alignment you'd still have some warning lights down on your panel by your right leg. NAV and EAC in particular would be on... When you're sitting on the ground waiting your CDU (bring it up on your right MFCD) needs to get up to 4.0.0.8, then you've got to hit your NAV button on the right MFCD in your CDU menu, then EGI button (forward of the stick), then flick your EAC on. That will ensure your aircraft is primed. Also, don't forget the markings on the HUD are different between laser guided and GPS guided... Laser will have the "ball" that drops into the center of the CCRP reticle with a countdown, while the GPS will have two carets within the CCRP reticle (minimum / maximum drop distance) with an indicator that moves around the inside to show where you are within your drop parameters. Some people have made that mistake- looking for the wrong style of reticle or trying to drop while outside of calculated drop parameters. :book: Also how are you setting up your profile? Are you doing it through dsms / profile / gbu- 12 then setting to ccrp- then changing settings to auto laze and laze time 10-12 seconds then saving? Or are you just going to one station and changing a profile for a particular weapon?

Originally Posted by SNAFU View Post This should be the airdrome IDs: 0 Airdrome_0 1Khersones 2 Saki 3Simpheropol 4 Razdolnoe 5 Dzhankoy 6 Kirovskoe 7 Kerch 8 Belbek 9 Krasnogvardeyskoye 10 Octyabrskoe 11 Gvardeyskoe 12 Anapa 13 Krasnodar 14 Novorossiysk 15 Krymsk 16 Maykop 17 Gelendzhik 18 Sochi 19 Krasnodar_P 20 Sukhumi 21 Gudauta 22 Batumi 23 Tskhakaya 24 Kobuleti 25 Kutaisi 26 MinVody 27 Nalchik 28 Mozdok 29 Tbilisi-Lochini 30 Soganlug 31 Vaziani 32 Beslan Anyone know if these are all still current? Reason I ask is I've been adding versions of this script to add airfields. Once I added the third iteration it stopped spawning aircraft at thode designated places. I know the script loaded since I have it changed to a c- prefix... predictably all subsequent aircraft are spawned with c prefixes. But they won't take off from those bases- in particular Krasnodar center, Anapa and Krymsk. I've used the names in a corrected post earlier in this thread. I've changed everything I can think of in terms of random numbers and airfield id's (up to 7-9) and in my last log the Anapa base returned a nil value. So just wondering how I can go about problem solving this?

There are a few different threads about stutters etc- and there are some subtle refinements that can be done in the nvidia control panel... I think if you look up "got stutters, odd lag" you'll find the thread and the recommendations. Granted I think it's an older thread now- but it's got some good insights. EDIT: Found it: http://forums.eagle.ru/showthread.php?t=68060

What if you "Force" the AI action? I haven't tried that but gave up with it too- not worth the hassle.

Funny how important some of these things are to us... but yes, I'm with you on this one. IF IT WAS THAT MUCH EASIER FOR EVERYONE WE WOULD ALL ALWAYS WRITE IN CAPS. :pilotfly:

was this the thread you saw? Here is what Seikdel did to get going again... http://forums.eagle.ru/showthread.php?t=94704 Specifically: http://forums.eagle.ru/showpost.php?p=1572740&postcount=24

and you're POSITIVE you've loaded the DX9 redist when given the opportunity upon installation? And repaired the C++ (I think it's repaired) when given the option upon install? Sorry- this is a VERY persistent crash and frankly I'm not seeing the usual suspects. And you're saying it crashes even when you haven't got the FC3 loaded... so this is a base world issue or a computer issue on your end. What about your DXDiag? Can you post that for ish and giggles?

Okay- your video drivers as well... they current?

Check to see if you have the latest driver here: http://www.gigabyte.com/products/product-page.aspx?pid=4305#dl You can check that against your device manager in windows...

Yeah I thought about that but totally different presentation. Just in case though: Try this Sam http://forums.eagle.ru/showthread.php?t=124577 Also Sam I remember that audio failure too. Do you have current audio drivers?

I haven't seen that error before so I have to walk through it with you from scratch... sorry. So if you remove the FC3 module- does it still crash on load?

Okay... couple things- I'm wondering how you actually installed the modules- you said you uninstalled the STEAM version and installed the ED version- did you rename the DCS folder after you did that? If not, do it. Have you actually installed the modules or did you just download them in hopes they would pick up automatically?

you able to start multiplayer?

Resetting SPI (TMS left) just disengages current SPI it doesn't boresight sensors (china hat back short). Pinky manages light configurations- to set profiles from your lighting panel. You may have position lights on steady and collision lights set to on but if pinky is set middle then your lights won't turn on. Mic switch would be necessary to get radio menus (I imagine since that's what it's only function is) and yeah cms auto is a waste. Cms is a 5 axis button controlling jamming(push in) as well as selecting programs (left -right) and start stopping selected program (forward-back).

Yup that prepare mission function is still my biggest suspect when I read these threads. Good call Stuka. Guys even if you didn't use prepare mission it sounds like someone did so its worth checking out.

There should also be a "crash" file- same place you grabbed those other two. Still seeing that direct x (dx I'm assuming is direct x) error to load a texture. Did you load the redist for dx9 when you installed?

Very diplomatic.

Did you load the redist of the DX? A lot of people skip it thinking their DX is 11 and reverse compatible.