Autogen locations, heights etc are built into the DSF files. If you are using HD Mesh, then my guess is that you may see some new artwork, but since the tile hasn't been recut, there will be no difference with heights (but there will be new buildings). For people not seeing the updated New York, try disabling HD Mesh and see if it works

 

Tried with and without the HD mesh. Same results. It's just a bug I guess, as some ppl are seeing the new, dense Manhattan (it's easy to distinguish here).

Well, my 2 cents:

 

From my observation (CAUTION: this is not official, nor had I time to ask Ben about it !!!!!!!):

• the new autogen is definitely there, but the scenery in New York is not fully "using" it, because the building heights are often - well - not set that high ... this is a "problem" of older scenery (and no different with HD mesh Scenery v3)
• quite likely, in Ben's screenshot he used some newer scenery, which used much more "real" building height data (maybe from experiments for X11 ?? ... because I clearaly know, that I supplied him that height data extracted from latest OSM ... and which at least in New York is quite good).

So ... quite likely the case is that the current scenery (default or HD Mesh) has simply not enough high rising buildings defined in it to make the new autogen shine. BUT, the new autogen gets still used wherever the scenery already references types which received an artwork update. Which is quite likely in more places than most of us "realize" (because everybody was expecting and looking for the perfect NYC skyline ... which didn't happen just trough plain magic).

 

UPDATE: and maybe its just because of different expectations, that some see "something" and others not :smile: (only by providing screenshots could we more objectively decide, if we all see the same or something different .... oh, and then we didn't even ask people to make sure the have no add-on scenery active at the same time).

 

UPDATE 2 : and after re-checking NYC ... If I look over to Manhattan from La Guardia, I wouldn't even say the skyline looks bad. Its just maybe still not the "real thing" (so, with latest OSM data, it could be even better).

Well, Laminar has advertised the new Autogen with screenshots for months now, including a conference where the new Autogen in NYC and Seattle was one of the main topics of 10.50. At no time anyone from Laminar stated that new data or anything else would be required - except for the 10.50 update, so I think we can rule that out.

 

It would be helpful to have screens from users who actually see the new Autogen, to make sure it matches what Laminar has shown. I for my part get exactly the same (building heights) as in 10.45 - there might be new assets but I couldn't care less at this point.

 

As I also don't see any new static AC, I strongly believe it's a bug.

At no time anyone from Laminar stated that new data or anything else would be required - except for the 10.50 update, so I think we can rule that out.

 

 

Ben just stated in a comment to a user's question on his blog:

 

 

User: For clarification, is the new city building autogen working for cities in the U.S. only ? If so, are there plans to expand it ooutside the U.S. ?

 

Ben: No – it’s broken in beta 1. It’s not working anywhere due to an installer bug. I’m working on this ASAP for beta 2.

 

It's the 2nd comment of this post http://developer.x-plane.com/2016/06/x-plane-10-50-beta-1-is-here-and-only-slightly-on-fire/#comments

Ahhhh.....

 

"No – it’s broken in beta 1. It’s not working anywhere due to an installer bug. I’m working on this ASAP for beta 2." - Ben

Ben just stated in a comment to a user's question on his blog:

 

 

It's the 2nd comment of this post http://developer.x-plane.com/2016/06/x-plane-10-50-beta-1-is-here-and-only-slightly-on-fire/#comments

 

Or that ... a Bug :smile:

Thats why it is called a BETA (maybe this example helps some users to understand, why its not always great to have betas)

 

(nevertheless: I am still quite sure, that the new autogen can give even better results with improved scenery data - because the result can usually never be better that the data its based on ....)

Ben has written some more about bugs:

 

http://developer.x-plane.com/2016/06/some-bugs-in-x-plane-10-50-beta-1/

new autogen issue, aircraft on the gates, plugin crashes... known problem know. fixed for b2

 

read here from Ben

 

http://developer.x-plane.com

It's kind of ironic that 10.50b1 arrives with the major content updates completely broken. It's not that there wasn't a long private beta. Oh well.

It's not that there wasn't a long private beta. Oh well.

 

Well, before release of beta 1, Ben wrote:

 

With any early beta of a major patch, I suggest that early adopters install it on a copy of their X-PLane folder and not the one they use to fly. This goes double for 10.50 because Jennifer, our Q/A head, is out of the office on a road trip. She was able to do a little bit of checking and we’ve tried to spot check it, but this release is more like the beta process from two years ago and not like 10.40 or 10.45.

So I assume it actually was not as long in a private beta as have been 10.40 / 10.45.

It's kind of ironic that 10.50b1 arrives with the major content updates completely broken. It's not that there wasn't a long private beta. Oh well.

 

This is not unusual for X-Plane. Some betas like the last two or three are solid, but the ones involving major changes are often a bit rough. I remember one that broke a bunch of plugins a while back, which was quickly patched. Just par for the course. They don't have the full range of consumer hardware, OS versions etc. for internal testing on Laminar, so some things slip through. Remember they develop on Macs. 

 

I know people get excited about new betas, but it's still best to approach these things cautiously. 

It's kind of ironic that 10.50b1 arrives with the major content updates completely broken. It's not that there wasn't a long private beta. Oh well.

 

It is kind of ironic, though you can't really criticize them for releasing a broken beta. The whole point of a beta is to reveal show stopping bugs and fix them before the final release. It was probably working fine during the private beta (how else were they able to post screenshots?), but something got messed up when they packaged the installer for Beta 1.

It's kind of ironic that 10.50b1 arrives with the major content updates completely broken

 

If you read Ben's comments...some major issues like autogen wasn't within 10.50b1 but rather in the installer itself. Lets give Ben & LR some breathing room, after all and as stated before, it's only Beta.

It's all cool guys. I am just anxious, and I want my toys.

My FPS has dipped something horrible overnight.