When I went to KPDX, my aircraft was sitting on top of a mound on the runway and everything around me was corrupted.

 

 

That's exactly how I'd describe what I am seeing too Jim (at OG39)...... With CRM deactivated, when I load a flight there, I'm put onto a badly distorted / gray 'blob', that is partially underneath the ground level.   No default airport, nothing.

 

 

 

 

As I stated in my post#33, I deactivated CRM and was still able to see FTX KJAC.  Strange.

 

Very strange indeed.  It seems there's perhaps an inconsistancy in how individual airfields are handled, when a region (or at least CRM) is deactivated.

 

 

That's exactly how I'd describe what I am seeing too Jim (at OG39)...... With CRM deactivated, when I load a flight there, I'm put onto a badly distorted / gray 'blob', that is partially underneath the ground level. No default airport, nothing.

 

Dave, keep in mind that Orbx regions contain (obviously among many other things) custom mesh.  One of the issues you'll run into is that Orbx airports expect that mesh to be active.  If the default mesh is close you should be fine.  If it's significantly different, there'll be larger issues.

 

Scott

 Ah, ok.  Thank you for the info. 

 

Can anyone provide a pic of what the MSE looks like at night?   

Here's a picture over Maryland near the Beltway (just north of Wash DC).  As I stated, you only get the default light which may or may not be accurate.  This one looks pretty accurate.

 

 

Best regards,

Jim

Well, to beat a dead horse, it would be absolutely amazing if someone wrote a tool to read the autogen from Orbx and write out autogen that would be used by photoreal.  I mean, FSX does it...sort of.  Probably be the tool of the year.  I'll shut up now. 

This is why I discussed this issue in a lengthy post elsewhere in the FSX Forum regarding MSE scenery (I might have moved it to the Photoscenery Forum where I plan to move this topic soon).  I use the SceneryConfigEditor.  This way I can disable/enable whatever scenery I plan to use during a flightplan or during a FSX session.  Only that scenery loads when FSX starts up and it is fast.  When I had 34 states all enabled and loading, it took around 20 minutes to select an aircraft.  Once an aircraft was selected, I had to wait longer to see the aircraft in the window then I could select the airport I wanted to depart from, time, and weather.  Once completed and hitting the FlyNow button, it took another 10 minutes (hey! I could be a little off on the time here but anything over a minutes loading and I think it's 10 or 20 minutes but I'm pretty sure the 20 and 10 minutes are pretty accurate).  Then, once you got into the air, the fps would suffer as the HDD's were thrashing trying to load all 852 GB's (or whatever).  Sometimes I saw a freeze or FSX was simply unplayable until the loading stopped.  So the SceneryConfigEditor is the way to go (you can use the Scenery Library too but this way you can make the changes BEFORE starting up FSX so things are quicker).

 

I also used the SceneryConfigEditor to place my States in Alphabetical order to make it a little easier to select the states I want to activate.  It also has a function where you can select the states you want to fly then save the config as something like the flightplan - KPDX to KSEA.  I tried this function but it worked sometimes and sometimes not.  Still the SceneryConfigEditor is a nice tool to have when you have a lot of photoscenery.  If you have ASE, it gets extremely upset when you disable the airports you had configured in ASE but I don't see any reason to activate FSDT KORD or KLAS or KJFK if I'm not going there as those airports WILL be loaded if activated in your Scenery Library.

 

Best regards,

Jim

 

Jim, I am having the same issues. Extremely long start up times and launch time after I select my aircraft as well. I have downloaded sceneryconfigtool. So basically to speed things up I only check the scenery area that I want to fly in and have the rest unchecked before I launch FSX?

Hi,

 

Just looked into this further.   Thanks for the suggetion but no, this is not the same issue.  These guys were getting no buildings with the FTX region activated.   As you said, this was due to the ObjectFlow failing to activate.  My ObjectFlow is activated ok in the DLL, and the airport is performing normally, when the FTX CRM region is activated.

 

However, when the CRM region is not activated, the OG39 airport does not appear at all (not just buildings; the ground image and everything is not there).

 

Basically, what I've learned here (which I never realized in 5 years of buying Orbx airfields), is that (for CRM at least), when you de-activate an FTX region, the FTX payware airfields in that region also deactivate, and do not show in FSX.

 

I just tried FTX OG39 with CRM enabled and disabled, and it looked exactly the same, with all objects showing up. So it definitely doesn't require CRM in order to function.

 

The blending is not pretty, but the objects show up just fine

 

OrbX place their objects using a special .DLL instead of the normal way. This is what allows them to switch out the 3D objects depending on conditions such as time of the year, time of the day, day of the week etc. So if the objects don't show, it means your DLL is not loading.

 

If you go to FSX folder in Appdata (where fsx.cfg is stored), you should have a file called dll.xml. In that, you should have this somewhere:

  <Launch.Addon>
    <Name>ObjectFlow_OG39</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path> (Path to your Objectflow.dll</Path>
  </Launch.Addon>

Also make sure the dll file is actually placed in the folder indicated. Also make sure OG39 is above Megascenery in the scenery library.

Thanks Jimmi.

 

It seems then, that the problem is experienced by some users, but not others.  I do have the objectflow appeaing in my DLL.XML;

 

 

 

<Launch.Addon>

    <Name>ObjectFlow_OG39.dll</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_OG39\Scenery\ObjectFlow_OG39.dll</Path>

  </Launch.Addon>

 

 

 

....but for some reason, it just is not working, when CRM is deactivated.

Jim, I am having the same issues. Extremely long start up times and launch time after I select my aircraft as well. I have downloaded sceneryconfigtool. So basically to speed things up I only check the scenery area that I want to fly in and have the rest unchecked before I launch FSX?

That's correct.  Just do not uncheck any default scenery as that could cause problems.

 

Best regards,

Jim

Here's a picture over Maryland near the Beltway (just north of Wash DC).  As I stated, you only get the default light which may or may not be accurate.  This one looks pretty accurate.

 

 

 

Best regards,

Jim

 

 

Thank you, Jim!    That does look fine.

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "The Photoreal Scenery Support Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.