XP11's g1000 crashes with Ortho4XP

[Dirk98 354]

Hello,

I have XP11's g1000 - related crash zooming it in/out in California with Ortho4XP/HD Mesh v4.

This is consistent, I tried it with US Ortho4XP project, I did Ortho4XP scenery/overlays myself - G1000 always crashes in California.

Interesting, but in UK (say around EGLL) g1000 works always fine with Ortho4XP scenery / HD mesh v4.

Did anybody observed this with Ortho4XP?

Thanks.

[dmarques69 316]

But in what plane? i found that very strange... you are using Ortho4XP and HD mesh v4 together? because you can only use one of them.

[Dirk98 354]

44 minutes ago, dmarques69 said:

you are using Ortho4XP and HD mesh v4 together? because you can only use one of them.

You sure you know what you're commenting on? There is no because, because they are different parts of the scenery structure, look up on the both of them, there are many tutorials and videos on the Internet and youtube in case you're interested.

 

 

Edited June 26, 2018 by Dirk98

[dmarques69 316]

9 minutes ago, Dirk98 said:

You sure you know what you're commenting on? There is no because, because they are different parts of the scenery structure, look up on the both of them, there are many tutorials and videos on the Internet and youtube in case you're interested.

 

 

So what catch your attention was this!? ok... Ortho4XP and HD Mesh are not compatible together, you only going to see one of them, your just wasting time and resources...

" Very important: both HD Mesh Scenery and usually any other photoscenery (like from Ortho4XP) qualifies as mesh scenery. X-Plane has the rule, that in the same location (and any 1×1 degree tile counts as the “same location”) at the same time you can always and exclusively have only ONE mesh active (and thus rendered). If you have more than one of them in the same location at the same time then X-Plane never mixes or merges them “on the fly”. Instead, X-Plane shows you the one with the highest priority in the scenery_packs.ini! Every other mesh or scenery (airports etc.) below the highest active mesh layer will not even get loaded at run time!

If you want to use HD Mesh Scenery v4 as you “generic” base layer for large areas (which is a good idea) and photoscenery (like Ortho4XP) for selected areas, then make sure that all of your Ortho4XP generated mesh tiles are sorted above(!) the HD Mesh Scenery v4 layer in the scenery_packs.ini!"

Good luck solving the crash issue.

 

[Dirk98 354]

 

You'll find it here how it works in principle

[Dirk98 354]

1 hour ago, dmarques69 said:

So what catch your attention was this!? ok... Ortho4XP and HD Mesh are not compatible together, you only going to see one of them, your just wasting time and resources...

" Very important: both HD Mesh Scenery and usually any other photoscenery (like from Ortho4XP) qualifies as mesh scenery. X-Plane has the rule, that in the same location (and any 1×1 degree tile counts as the “same location”) at the same time you can always and exclusively have only ONE mesh active (and thus rendered). If you have more than one of them in the same location at the same time then X-Plane never mixes or merges them “on the fly”. Instead, X-Plane shows you the one with the highest priority in the scenery_packs.ini! Every other mesh or scenery (airports etc.) below the highest active mesh layer will not even get loaded at run time!

If you want to use HD Mesh Scenery v4 as you “generic” base layer for large areas (which is a good idea) and photoscenery (like Ortho4XP) for selected areas, then make sure that all of your Ortho4XP generated mesh tiles are sorted above(!) the HD Mesh Scenery v4 layer in the scenery_packs.ini!"

Good luck solving the crash issue.

 

Did you notice this post when quoting the first one from that thread?