ramjet

Hello, I have finally been able to get to the cause of my problems. It was my root FSX registry. I will not be surprised if something shows up later but for now I have a restored FTX Central and it was fixed using the Windows regedit registry repair tool. I was coached through the process by an Orbx forum member and was able to redesignate my FSX root. It is still a mystery how the scrambled files happened but I think I have my fully functioning fligh sim back. Thank you again to Jim and all who replied to my questions and offered help. It was frustrating but I hope others can be helped by the information you shared and my successful outcome. good flights, Cal

Thanks for the link Jim. I tried what Ed recommended but it didn't work for me. Wolter at Orbx also had a suggestion but it also failed. Something is really out of order in my system and files are getting misplaced. Maybe I should go to work for Goldman Sachs. I am asking Orbx if I can just reload a region and a library update to get a fresh install of FTX Central. If that works I'll tell the world. good flights, Cal

Thanks, I did that but no change. Cal

err uh....anyone know how to fix or replace a non-working FTX Central ( Orbx ) ? When I open it I get an alert that " object reference not set to an instance of an object". The fun never ends does it? good flights, Cal

+1 I hope in turn I can become helpful like Jim.

Hey all, I'm happy to report that I finally got the Metroliner in its entirety. It took a lot of trying things and I was ready to just give up and put it away. I installed the clean dll.mxl that Jim worked out for me but I still couldn't get the lights, fuel gauges, electrical panel. I tried Jim's idea to check to see if I had object flow with winter flight at Stewart, CZST. When it opened my plane showed up high over the airstrip and so I decided that FTX Central was messed up. I was right, it wouldn't open and there was an info box saying a file was missing so it couldn't access FTX Central. It was different files which I located and moved to Scripts then I reinstalled FTX Central.exe many times but still it wouldn't open. I rebuilt FSX.cfg, I then had to run chkdsk because my drive was faulty, I did a system restore , and I reinstalled ORBX Library, and reinstalled the Metroliner. I restarted but I had no yoke. I turned it off and walked away. I came back, checked all the connections and rebooted. When I opened FSX and selected the Metroliner, it was all working. I took a 1/2 hour flight playing with the lights and enjoying the panel, landed and started this report. I know I didn't do this in a smart way. I just tried anything I could think of because nothing was working and I had multiple issues. I don't know why it all happed but Jim really helped me with his corrections to my messed up files and good suggestions. Thank you, its great to be flying again and enjoying all that the Metro offers. good flights, Cal

Hi Jim, Your determination to see me through this is humbling. I should be in front of the computer and not relying on memory. On my computer Drive E is labelled Games so I think I've made an error listing it as E:\Games which would explain why we see entries E:\Program Files\ORBX and not E:\Games\Program Files\ORBX. I can believe I've made several wrong turns and I will go carefully back to your earlier postings and work forward. I'm confident that a solution is at hand. I sure hope this is helpful to someone else who has issues. Thank you, Cal

Hi Jim and all, OK sir, I'm going back to school at the first chance I get and I will follow line by line what you advise. Darned if I know what crazy thing I might have done. I did open the gauges file in FSX two days ago and found two cab files which contained annunciator files and gauge files so I copied them to my Metro panel, long after all of this started. I do have a Microsoft Flight Simulator X\Addon Modules folder and I will look for the MM3SM.dll FSX is installed in my computer on E:\Games\Program Files ( Program Files is FSX, I bought the computer already set up with FSX, used ) Good idea to check CZST, I don't even know what a junction link is but like I said, I will follow your advice line by line. I really appreciate your efforts Jim. Regarding the newest installation: Fresh download, copy to desktop, open and follow prompts to successful install. I did not deactivate virus software. I will happily start over if you think I messed something up. Cal

Bad news I'm afraid. Nothing changed after making the corrections to my dll file. It flies but the panel is dark and no interior or exterior lighting, and only some of the gauges work. Cool plane but I'd rather fly one with all systems working. good flights, Cal

Thank you Jim, I thought that the simbase doc needed to be the last line in the Metro section and when that didn't work I actually looked at that FSUICP and wondered if might be in the wrong place since I added a fresh install of that last. WOW, that would be really great if such a simple change can solve my problem. I wasn't even aware I was missing accusim or object flow so now I'm even more jazzed. I've had several good flights and landings with the Metro but gauges, lights, and moving needles will make it even more fun to control and fly.Thank you, I'll happily report back on my success. good flights, Cal

Hello forum friends, Here is my dll.xml as Jim requested. Maybe someone will spot the cause for my problem with the Metroliner's lights, fuel gauges and electrical readouts. Thanks for your efforts. Cal <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>ObjectFlow_NZQN.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>E:\Program Files\ORBX\FTX_NZ\FTXAA_NZQN\Scenery\ObjectFlow_NZQN.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow_05S.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>E:\Program Files\ORBX\FTX_NA\FTX_AA_05S\scenery\ObjectFlow_05S.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>E:\Program Files\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow_KMRY.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>E:\Program Files\ORBX\FTX_NA\FTX_AA_KMRY\scenery\ObjectFlow_KMRY.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow_KRDD.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>E:\Program Files\ORBX\FTX_NA\FTX_AA_KRDD\scenery\ObjectFlow_KRDD.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow_CZST.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>E:\Program Files\ORBX\FTX_NA\FTX_AA_CZST\Scenery\ObjectFlow_CZST.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow_SAK.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>E:\Program Files\ORBX\FTX_NA\FTX_NA_SAK05_SCENERY\scenery\ObjectFlow_SAK.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow_W52.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>E:\Program Files\ORBX\FTX_NA\FTX_AA_W52\scenery\ObjectFlow_W52.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Objectflow_KBVS.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>E:\Program Files\ORBX\FTX_NA\FTX_AA_KBVS\Scenery\Objectflow_KBVS.dll</Path> </Launch.Addon> <Launch.Addon> <Name>ObjectFlow_7S3.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>E:\Program Files\ORBX\FTX_NA\FTX_AA_7S3\Scenery\ObjectFlow_7S3.dll</Path> </Launch.Addon> <Launch.Addon> <Name>A2A Feel</Name> <Disabled>False</Disabled> <Path>Modules\A2A_Feel.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>AccuFeelMenu</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\AccuFeelMenu.dll</Path> </Launch.Addon> <Launch.Addon> <Name>RAZBAM Metroliner System Control</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Addon Modules\MM3SM.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> </SimBase.Document> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon>

No flying time lately. I will post again asap. Thanks again, Cal

No time to fly the last few days but I will do as you suggest tonight and report back. I checked the forum at Razbam and others have reported the same issues so we may be about to help a bunch of simmers enjoy their Metro even more. Jim , very interesting that you made the problem occur by moving out the dll.xml file, that may be my issue as well. Thanks for your efforts on my behalf. I am visualizing a complete panel with beautiful annunciater lights and working gauges and lighting. good flights, Cal

Thanks all, in your post Bjoern, you mention the inverter switches. I have clicked those up and down over and over, no change. I am reading the manual and I am doing what it says but still no change. I'm trying to love this plane but its kind of hard when it doesn't work. Any more suggestions? good flights, Cal ....see, I'm trying to stay cheerful.

Hi Jim, Thank you for your help, it was very gracious of you and I followed your instructions and saw the dll just as you described but my copy was already correct so I'll need to look further. I don't have any lights and electrical readings and my fuel gauges are frozen. Its a mystery to me When it does get fixed I will happily share the solution. good flights, Cal