Here i am again! :-)Installed flightcrew yesterday as well and when i made a flight yesterday, it worked.But today - no way. Usually when the message RADAR CONTACT comes up - it continues reading in Flightcrew and you hear a "bing". However - today it just stops at RADAR CONTACT and nothing more happens. Tried to continue, but no flightcrew, just the "ordinary" controllers and chat.Having tried a couple of times, i re-installed the flightcrew - ofcourse having to overwrite what was already there - and it didn't help. (Have check'ed FAQ without finding anything).Are planning my flights using FSnavigator 4.5.What's going on? - after one hour fiddling with this, i lost every interest in flying today. On top of this - at my final attempt FSmeteo wouldn't download the weather... - Anyone putting needels in a Lars Kl

Lars,You nay have originally compiled the files without FltCrw. Try recompiling and test again.

Hello Scott, As I am also using FSNav, 4.1.x on the DLL, and FltCrew where do you find the info to compile the RC adv with FltCrew? I don't believe I did that in my KSLC--KORD flight last night. Yet it seemed to work fine.SOS or maybe MAYDAY Scott.

Blais,With FltCrw installed, it automatically is included in the afventure when compiled.When you reinstalled RC, you should have also reinstalled FltCrw afterwards (as I said in the post you had about this), which sets up the RC files to include FltCrw. Then complie the adventure and you're set.

Roger Scott. Thanks

Sorry if i'm stupid, but with "compiled", do you mean having created the adventure with the files installed? If so, the files were already installed.Yesterday evening it worked, so i'm baffled why it doesn't today.. Also a strange thing - when i have created an adventure, i usually first change the situation from the day before - to another plane, the right time (today) etc. and save that, before loading the adventure. If i for some reason have to restart it, i have before always been able just to load the andventure and then start from where i left. But now i get the situation i saved the day before.. A small thing, just mention it, as i don't know why it acts different from my last installation.I can live with the last thing, but it's a little sad with Flightcrew.CheersLars

Lars,When you say it worked yesterday and today it doesn't, do you mean with the same adventure, or a new one compiled since the reinstall?

I mean a new compiled job, created following the same procedure as i did yesterday and always does... I did in fact compile the trip 2 times today - same route, from Mobile, Alabama to Akron, Ohio.Have check'ed the initialize_fltcrw.txt file - and it's not there, the problem is...CheersLars

Lars,I can guarantee when you reinstalled RC, you didn't reinstall the FltCrw txt files.It's easy enough to check to see if you have FltCrw defined for RC. Look in FLEETWOOD_EXTERNAL_MAIN.TXT and see if you have "gosub fltcrw" and without a semi-colon (;) in front of it. If not, you don't have FltCrw defined.Unzip the FltCrw *.txt files (all of them) into the RCexternal directory again, then recompile.

Hi Scott..This is how the content of the txt-file looks like:external_main: gosub fltcrwreturn include "..externalmain_fltcrw.txt" ;briefs/checklists include "..externalmain_vc.txt"-seems to me, it looks right. One thing though - perhaps because i don't know much about coding, but how does it know, what drive to look at. How does it know what drive to look at? But - then again, it did work 2 days ago.. Can airplanes or certain panels cause any troubles for the program? The only difference between the first flight and the "sick one" yesterday, is the kind of plane. It doesn't seem logical to me, but it's the only difference. Haven't tried this, as i'm hardly awake yet... :-)CheersLarsK

HiToday, with a new flightplan (KCAK-KDEN), a new plane and another panel - as the only different from yesterday, it worked... Haven't made any other changes - really!! This is very strange, but i hope it stays this way... Sorry for all the trouble!! :-)CheersLars