Jump to content

Scott B

Members
  • Posts

    74
  • Joined

  • Last visited

About Scott B

  • Birthday 01/23/1964

Profile Information

  • Gender:
    Male
  • Location:
    TX
  • Interests:
    Aviation & computers, of course. :-)

Scott B's Achievements

Advanced Member

Advanced Member (3/6)

5

Reputation

  1. Does the following look about right? Installed products: FSX, Libraries 170701, FTXG Base, Open LC NA, CRM, NCA, NRM, PFJ, PNW, SAK, SCA and KSQL (among many others) Highway near KSQL: N37° 30.70' W122° 15.22' OpenLC-NA Night Lighting enabled and New Night Lights enabled (default): OpenLC-NA Night Lighting enabled and New Night Lights disabled: OpenLC-NA Night Lighting disabled and New Night Lights disabled Open LC-NA Night Lighting disabled and New Night Lights enabled (preferred?)
  2. Please move my previous post to FSX or remove it entirely as it is explained here. Apologies.
  3. Ditto. FTX Global Base, Open LC NA, CRM, NC, NRM, PFJ, PNW, SA, SC and individual airports all with lighting features as I recall. Throw in "FTX Day" option, "FTX Night" option, "FTXG Lights" options, "FTX Lights" options, and now the above mentioned "compatibility" options, well, it seems like a lot of variables, and I tend to forget how they work together. I appreciate the dedication to updates and I sincerely don't mean to make things unnecessarily confusing but, trial and error seems exhausting. Recommended setting for best performance and visuals considering the variables? And maybe an explanation as to what is still relevant/beneficial?
  4. Thanks Orbx team for doing a great job. Great product, great support, easy transitions, straight forward, simple. I was surprised to see the second email because I didn't realize there was an issue with the first one. Maybe folks need to also consider imaging their drives from time to time. Thanks for your efforts.
  5. So what about FTX airport conflicts? I have KSEZ payware and I'm about to install the latest NA Freeware pack which also contains KSEZ. Just curious. Thanks. Scratch that. The PDF associated with the NA Freeware Pack explains: "Italic → not installed by this version’s installer as the airport is now available as a separate payware release or part of a Region pack; e.g. KBHB" KSEZ is italicized therefore won't be installed with the Freeware Pack. Apologies and thanks.
  6. Ahhh... thanks Stewart. I wasn't aware of that. Cool.
  7. Everytime I run FTX Central the "dll.xml" file gets fatter and fatter! Seems the below entries continue to repeat over and over. Anybody know why or how to stop it? Everything works fine, latest patches and libraries installed. 77S, CBB7, OR57 are the only airports that continue to load up the file. Just curious. Thanks, Scott <Launch.Addon> <Name>Objectflow_77S</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_77S\Scenery\Objectflow_77S.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Objectflow_CBB7</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_CBB7\Scenery\Objectflow_CBB7.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Objectflow_OR57</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_OR57\Scenery\Objectflow_OR57.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Objectflow_77S</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_77S\Scenery\Objectflow_77S.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Objectflow_CBB7</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_CBB7\Scenery\Objectflow_CBB7.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Objectflow_OR57</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_OR57\Scenery\Objectflow_OR57.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Objectflow_77S</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_77S\Scenery\Objectflow_77S.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Objectflow_CBB7</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_CBB7\Scenery\Objectflow_CBB7.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Objectflow_OR57</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_OR57\Scenery\Objectflow_OR57.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Objectflow_77S</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_77S\Scenery\Objectflow_77S.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Objectflow_CBB7</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_CBB7\Scenery\Objectflow_CBB7.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Objectflow_OR57</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\FSX\ORBX\FTX_NA\FTX_AA_OR57\Scenery\Objectflow_OR57.dll</Path> </Launch.Addon>
  8. Thanks seby.h! I take a lot from these forums so it's nice to finally give back!! Regardless of this glitch, Orbx still makes a fantastic product that really does transform the sim. Funny... Ed actually said "it's not the end of the word".... He was right about that one! Poor attempt at humor on my part. Scott
  9. Hi Ed. Hey, it's become very clear to me now that there is a big difference between "triple-installer" and "module-installer". I've learned a lot. Not being a programmer, it's easy to lump those two terms together, as it all looks like an installation issue to a regular guy. I hope you can see that from the customer standpoint. The different module-installers certainly explains why the 1WA6 installation ignored the missing blank line, as GeorgeM hinted toward earlier in this thread. I'm still not sure what program if any, removed the blank line from the bottom of my (our) xml file but, unless you note otherwise, I see no reason why it shouldn't always remain there. Like you said, "It's not the end of the word...." Thanks, Scott
  10. Thanks for that!. Glad it worked for you! I hope it works for others that need it and hasn't caused more trouble than it's worth. That was never my intentions. Scott
  11. Hi Griphos. Just in case you aren't aware, the <CR><LF> is hidden and can only be seen in notepad ++ or similar. To answer your question, if you view the file with notepad ++, you should see it just after </SimBase.Document>. I would back up your xml file first, then just edit it with standard notepad (you won't actually see any <CR><LF>). Just put your cursor right after </SimBase.Document> at the very bottom and press Enter to create a blank line below it. Scott
  12. If memory serves me correctly, mine did not rebuild a new xml file either. It did, however, back-up up my original by renaming it to "DLL_BeforeModInstaller.xml". The way I found to "rebuild" the xml file was to reinstall the latest libraries after installing KJAC. (But rebuilding it does not restore it to full potential). You will then indeed have a new xml file, but..... the contents of that file will have no reference to third party add-ons like FSUIPC, A2A, or even FTX airports that haven't converted to the new unified object flow. You will have to re-install all of those, as Ed mentioned, to get those lines automatically added back into your new xml file. The third party add-ons aren't really uninstalled, it's just that FSX will no longer know where to find them since there are no references to them in the xml file... like removing a desktop shortcut as opposed to uninstalling a program. I'm sure you are aware of this... just in case someone else isn't.
  13. Hi Matthew. First you must find and back up your current file, just in case. In fact, it's not a bad idea to backup all of the files in that folder along with the dll.xml file. See GeorgeM post earlier to find the file and check out the link from PMDG associated with that post as it describes how to properly view and edit the dll.xml file. Once you've located the file, EDIT it with notepad (notepad worked for me, but I also used notepad ++ as a reference) and place the mouse cursor at the end of the bottom line that should read "</SimBase.Document>" (without the quotes). Simply press Enter to create one blank line at the bottom and save the file with that blank line in place. Again, make sure you have a backup copy just in case. The installer should run without the error message... hopefully!! At least mine did. That said, if you have any other issues with the dll.xml file then the installer may also see those issues as a stumbling block. If you already have a blank line in place then I don't have a solution but suggest you read the PMDG site to troubleshoot. Thing is, if you've had no other issues with triple-installers in the past, then your dll.xml file is probably OK except for the absence of the blank line at the bottom that hangs up KJAC. I really hope this works for everyone. It worked for me. Lot's of trial and error! So, if you happen to get the error message even after adding the line, don't install KJAC just yet! Make a point to discover what else may be a problem with the xml file first. Let us know how it works.
  14. I should also point out that, with a blank line in place at the bottom of the xml file, not only does the installer run without the corrupt xml message, it also properly removes the KJAC entry from the xml file as well. My apologies to Ed and Orbx as it seems there was an issue with my "dll.xml" file after all... on both of my machines! In my defense, I'm not sure I would call it a corrupt xml file, especially since other triple-installers haven't been affected by it. Just to be clear and for comparison, I tried 1WA6 triple installer again by first backing up my current "FTX_AA_1WA6" folder and then replacing it with one from April that contained the ModuleInstallers. Then I made sure my "dll.xml" file contained the 1WA6 entry and also made sure there was not a blank line at the bottom. 1WA6 again installed perfectly. Seems there are some subtle differences between the KJAC and the other triple-installers. Thanks Scott
  15. I think I have found the issue, at least on my systems. It seems to have something to do with the absence of a blank line at the bottom of the xml file. I restored a backup copy of the folder "FTX_AA_KJAC" that I had on hand from April (which contains the ModuleInstaller files). I then restored a "dll.xml" file I had on hand from early July. Through process of elimination and by using ExamDiff, I discovered that the KJAC 1.10 installer does not play well with a "dll.xml" file unless it has a blank line at the very bottom. That's the only difference. Remove the blank line, and I get an error message. Add the blank line, and the installer works perfectly. The recent release of 1WA6 triple-installer did not seem to be bothered by the absence of the blank line. I had installed that just prior to KJAC 1.10. So it appears for me, the issue was one blank line. Does that make sense to anyone? Scott
×
×
  • Create New...