Jump to content
warchild

OpenScenery no longer recognized by Overlay Editor. +

Recommended Posts

Ok, couple of things.

Overlay Editor just flat refuses to recognize that OpenScenery exists. Any old OSX files that may have been being used are unreadable and discarded. I have reloaded the scenery, reloaded overlay editor, reinstalled OSSX, you name it. Its just not there to be used.. Latest OSX update was tonight.  Seems the initial OSX install didnt install all the files, but i believe the update solved that issue.  Will keep hacking away to see what i can find..

Whiskey Blue.

  • Thanks 1

Share this post


Link to post
Share on other sites
2 hours ago, warchild said:

Overlay Editor just flat refuses to recognize that OpenScenery exists. Any old OSX files that may have been being used are unreadable and discarded. I have reloaded the scenery, reloaded overlay editor, reinstalled OSSX, you name it. Its just not there to be used..

Interesting.  I wonder whether OE is running out of memory, though a crash would be more usual in that case. Perhaps it can't handle the large groups of seasonal REGION entries. I have a tiny involvement with OE, as I recently rebuilt the Mac version to run on the latest macOS (it was failing to launch) so if I get a moment I'll see whether a fix is obvious. Otherwise, Jonathan (Marginal) will have to be involved.

2 hours ago, warchild said:

Latest OSX update was tonight.  Seems the initial OSX install didnt install all the files, but i believe the update solved that issue.  Will keep hacking away to see what i can find..

Not sure what you mean. I haven't made any updates to OSX since the 6th March when I fixed this issue.

Best wishes and thank you for spending time testing,
Austin G.

Share this post


Link to post
Share on other sites

Very cool. Thanks Aussi.. 

I discovered this when I opened up RJOA v1.1 in OE, and there were eight or ten objects it couldnt find: all OpenSceneryX objects. I then decided to add in Objects from OSX, and it wasnt listed with the libraries.  I checked in WED, and that worked fine ( except for my inability to do anything right ), so I went back to OE and OSX was gone again.  RJOA (Hiroshima) is an odd duck. The author created it with WED but it isnt editable in WED unless your adding objects. So it isnt very editable in OE either, but i needed polygons and forests, which are OE's forte. I finally got my editing done ( you need to restrict lines in the terminal area of the airpiort ) so its on to another airport that needs love and attention.. I'll look forward to your findings.. 🙂

Whiskey ..

Share this post


Link to post
Share on other sites

good question. I'll reinstall it after i awaken ans see what i can see.. It worked as of a month ago when i updated both eagle air (6k5) and Bend Muni ( kbnd), so it should, however, I just updated my motherboard three days ago so things may havchanged..

Share this post


Link to post
Share on other sites

Well, i couldnt sleep. Ever have one of those nights where you find yourself having a deep philisophical conversation with a warmed over stack of pancakes as the sun comes up?? Yeah! Well.. I uninstalled 2.5B1 and installed 2.4. Sttarted up OE and everything worked fine. OSX was listed among the libraries and everything was happy, SO! I uninstalled 2.4 and reinstalled 2.5B1 and had to run it twice because the first time it hung at 90% of the installation. However, with full installation of 2.5B1 there were missing objects reported by OE and OSX was not listed as one of the libraries..

The funny thing IS, OSX shows up in WED. Why the one and not the other?? I know theres a basic conflict between the two. You can add poly's and objects from OE AFTER you edit with WED, but anything you do in OE before editing with WED gets erased, so I was careful about that.   I'm no programmer and after my trip to the hospital last october, I aint nearly what I used to be, so, i'm nearly useless there. I'll keep poking around though and see what i stumble across..

Qd43yPO.jpg

 

vUPteuZ.jpg

Edited by warchild

Share this post


Link to post
Share on other sites

Could you try something for me: Re-run the OpenSceneryX installer, and disable seasons, then let the installation complete. Then re-run OE and see whether that makes a difference.  I have a theory in mind…

Share this post


Link to post
Share on other sites
17 minutes ago, warchild said:

You got it.. ( nope, still cant sleep ::LOL:: )

Right. I think what's happening is this.

When implementing seasons (using REGIONs in the library), because of the way libraries work we have to put all the seasonal overrides first in the library.txt file, and the main bulk of the library comes at the end after a REGION_ALL directive to tell X-Plane that the remaining items should be shown in all other cases.  It sounds like OE doesn't understand that everything after a REGION_ALL should be generally available and is therefore ignoring everything.

Ok, simple in theory but I bet it's not going to be quite so simple to fix OE 🙂  I'll take a look and see whether it's within my skills.

For the moment the advice is to disable seasons in OSX before building scenery if you want to use OE.

 

Share this post


Link to post
Share on other sites

ok, its hanging on /objects/aircraft/props/regional_commuter/fokker-50/japan_{{airlines/object.obj.

Ok, I suppose its to be expected, but OSX works with seasons disabled. Maybe it's bad news, but it could be some type of pointer to the actual issue as well. Theres a fundemental difference between the way seasons are being loaded and the rest of the library being loaded, and we need to adjust whatever is causing the hickup in the seasons. Let me know what youd like me to run and i'll make sure its done..

Share this post


Link to post
Share on other sites
4 minutes ago, aussi said:

Right. I think what's happening is this.

When implementing seasons (using REGIONs in the library), because of the way libraries work we have to put all the seasonal overrides first in the library.txt file, and the main bulk of the library comes at the end after a REGION_ALL directive to tell X-Plane that the remaining items should be shown in all other cases.  It sounds like OE doesn't understand that everything after a REGION_ALL should be generally available and is therefore ignoring everything.

Ok, simple in theory but I bet it's not going to be quite so simple to fix OE 🙂  I'll take a look and see whether it's within my skills.

For the moment the advice is to disable seasons in OSX before building scenery if you want to use OE.

 

Perhaps its simple in theory, but i do believe your onto something.. cool. seasons disabled for now.. Will wait for an update to attack the problem again..  Back to poking and prodding :)..

Share this post


Link to post
Share on other sites

Trying to track down another issue, I just found that the Version of OE that Aussi did for Mac OS Mojave, no longer shows OpenSceneryX objects or in the Pulldown. And yes Beta V4.0.0 is installed and working in X-plane and WED

mx6hnxo.pngMNw0ayq.png

Share this post


Link to post
Share on other sites

It's as I thought - OE doesn't understand the REGION_ALL statement in the library. Which is not particularly surprising as it's not documented anywhere and seems to have been implemented and disseminated by rumour and magic. I heard about it via other seasonal packages and the Four Seasons plugin.

So, not too sure what to do about this. I am using REGION_ALL consistently with other packages that use it, but because it's not documented, I don't know how it should behave under all circumstances. So it's a little tricky to implement the "correct" behaviour in OE. I'll see whether I can get any more info out of the X-Plane team.

Share this post


Link to post
Share on other sites

Got some input from the X-Plane team, and it turns out that REGION_ALL doesn't exist after all! So I've built a new release that uses a different mechanism.  Just re-run your existing installer, and re-test the new version, including in OverlayEditor.

Share this post


Link to post
Share on other sites

OK, so I'm getting snowy white trees in winter aand no snow on the trees when terraMax is turned off, so the basic mechanism is working. I'll start testing changing seasons.. Great job Aussi.. 🙂

Tbin33F.png

 

F2v6Mol.png

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.



×
×
  • Create New...

Important Information

Please read the Terms of Use