On 12/23/2019 at 6:23 PM, Pete Dowson said:

Okay, thanks. Would that be the AFD file provided with Orbx EGLC, or could there be another? 

So maybe I only have to figure out why they (and some other parts) are higher than the rest of the airport (runway included), and perhaps, if it is a separate problem, why the colour is all wrong.

I don't really understand is how two products from the same supplier don't work together. One of the things you hope for when buying them so is that they match.

Thanks,
Pete

 

It looks like the ORBX team failed to test all their add-on airports for TB GB because most require that you disable .bgls to avoid terrain issues. By now one would think that they would avoid this, but I'm going to blame the rush on the new sim that's right around the corner. They are about to lose a lot of sales, so they are rushing out these add-ons without fully testing them. They did the same thing with AU v2.

Edited December 26, 20196 yr by DJJose

I am not a fan of scenery without seasons I may just as well go to XPlane, but I thought I would try the local TE scenery Midlands and I am not blown away.

https://www.flickr.com/photos/154944674@N05/49277924216/in/dateposted-public/

Green roads ???.

https://www.flickr.com/photos/154944674@N05/49277451803/in/dateposted-public/

Just shows how good the GB region is with seasons.

https://www.flickr.com/photos/154944674@N05/49277451978/in/dateposted-public/

My sim is set to PC date and time winter now, but I had to change to summer this would look odd otherwise snow on one side.

16 minutes ago, DJJose said:

It looks like the ORBX team failed to test all their add-on airports for TB GB because most require that you disable .bgls to avoid terrain issues. By now one would think that they would avoid this, but I'm going to blame the rush on the new sim that's right around the corner. They are about to lose a lot of sales, so they are rushing out these add-ons without fully testing them. They did the same thing with AU 2.

Nonsense.

The payware airports all require that Verify files is carried out on them before they are used with TEGB.

Part of that process disables all conflicting files.

One can always ask a question at the Orbx forums, instead of inventing an answer to post on these forums.

 

14 minutes ago, Reader said:

Nonsense.

The payware airports all require that Verify files is carried out on them before they are used with TEGB.

Part of that process disables all conflicting files.

One can always ask a question at the Orbx forums, instead of inventing an answer to post on these forums.

 

It's not entirely bug free yet as a process I dont thing, but come on this IS a first world problem and terrain issues are not exactly insurmountable 😉

18 minutes ago, Reader said:

Nonsense.

 

Maybe only to you but not for someone like me who has been a customers since ORBX sold DVDs and shipped them from AU. Sorry to burst your bubble.

43 minutes ago, Reader said:

Nonsense.

The payware airports all require that Verify files is carried out on them before they are used with TEGB.

Part of that process disables all conflicting files.

One can always ask a question at the Orbx forums, instead of inventing an answer to post on these forums.

 

I don't agree with that UK2000 and AEROSOFT and others should now update there product to fit ORBX TE, no it should be the other way round ORBX should have tested with the airport currently available in the UK, just so happens I always turn off ORBX bgls for my airports for my AI this can cause problems.

6 minutes ago, rjfry said:

I don't agree with that UK2000 and AEROSOFT and others should now update there product to fit ORBX TE, no it should be the other way round ORBX should have tested with the airport currently available in the UK, just so happens I always turn off ORBX bgls for my airports for my AI this can cause problems.

It's not reasonable to expect Orbx to provide support for other Devs products, although that would have been nice if they did (and I would have done so if I had been able to beta test it.  If other Devs don't want to make their airports fit, (and they are under no obligation to do so), then we are stuck making it work ourselves.  Half the trick is understanding what add-ons are in use on any particular PC and how they work so any potentially conflicting elements can be resolved.  There's enough knowledge here and on the Orbx forums to accomplish that.  And the Orbx Dev is being very active in resolving issues which is a very positive thing.

The main problem has been a lack of autogen.

This has been traced to three products which adversely affected autogen on a worldwide basis due to a misunderstanding acknowledged by their developers. These were two Aerosoft airports and Godzone New Zealand. All three have now been updated to prevent this happening and the issue has gone away.

It should be noted that none of them are anywhere near Great Britain but nevertheless had that effect which also spread to other parts of the world.

The Orbx payware airports have all been updated to replace the missing autogen around them and these updates are applied when Verify files for them is run. Essentially, the airports' photo inserts have had the excluded autogen added to them. 

UK 2000 airports have their own photo inserts, which unfortunately also have the effect of removing the TEGB autogen around them.

This was far less obvious when used with the previous most popular UK photo scenery product, which did not include autogen.

To state that Orbx have rushed out the TEGB products without considering any addon airports is simply not correct. Any long term Orbx customer must be aware that their regions add a full set of enhanced airports and TEGB is also another region. Adding further third party airports over the third party airports added by the regions will require steps to be taken to prevent the first third party airport interfering with the second in the same place.

Unlike many developers, they maintain a Compatibility forum to specifically address compatibility with other developers' products. The sections on EU UK products can be applied in exactly the same way to the TEGB airports, so there is already a wealth of information available, gathered over years and kept for customers to refer to.

Edited December 26, 20196 yr by Reader

13 minutes ago, Reader said:

UK 2000 airports have their own photo inserts, which unfortunately also have the effect of removing the TEGB autogen around them

Correct, I was going to ask Sascha privately if they'd provide a grouped set of autogen files to add to each Uk2000 airport to fix this.  They may not do it, especially for competing airports, but if not UK2000 users should look to the UK2000 forums where I'll look to list the necessary files that people will need to add manually.

If there is just one thing I hope for in MSFS it's an end to various developer's  stuff not playing nicely together. They seem to me to be all in their own little world (sorry, no pun intended) and have no regard for the mess they create. We all have our own 'usual suspects'.

2c

Carry on chaps.

1 minute ago, Ron Attwood said:

If there is just one thing I hope for in MSFS it's an end to various developer's  stuff not playing nicely together. They seem to me to be all in their own little world (sorry, no pun intended) and have no regard for the mess they create. We all have our own 'usual suspects'.

2c

Carry on chaps.

sweet dreams! 😉

35 minutes ago, kevinfirth said:

sweet dreams! 😉

Yeah, the Christmas spirit got the better of me.

1 hour ago, Reader said:

To state that Orbx have rushed out the TEGB products without considering any addon airports is simply not correct.

Not any, but EU airports in their own catalogue. There should be no reason for me to have to go to the FTX compatibility forum to find out how to make their EU add-on airports blend with the new TE GB. It's not mandatory, but maybe good business.

You do not need to, just verify files for each one.

So what are we saying developer A makes a new scenery product so devs B C D that have products that have been on the market for years now have to update them for dev A.