Just make sure you report it up the proper channels. They have fixed their stock and premium content before and they will again.
It is good to point things out so they know they should look into fixing them.
The answer to, “Well why didn’t Asobo do this in the first place?” is always manpower.
They need folks like you to test and point things out to them.
They got dozens of airports made for release. Some were better than others. Some ended up feeling rushed. They probably were.
You have proved your case here.
We just aren’t here to help you marinate in how annoyed this issue makes you feel. There’s not much we can do about it except say, “Yup, those are some missing features you have pointed out, that is a legitimate issue, and it may be months before you see a fix because of how their update schedule works. File a support ticket so you know they have been made aware.”
I don’t seriously disagree in the slightest but I presume there were reasons they were left out on the day one launch. I presume somewhere down the line Asobo thought they would leave it to third party developers to upgrade the airports, as is being the case.
Yeah you can feel like you’ve been ripped off paying for these default handcrafted airports if you like but it comes back round to the fact you haven’t paid very much for them. They’re not perfect but they’re cheap.
Whilst the quality of some ‘premium airports’ could & probably should be better considering we paid more for them, my biggest annoyance is the performance of the big one’s like JFK & Heathrow. I rarely dip below 50fps but the few big airports destroy my framerate even after considerably lowering the settings.
I know there’s a limit to what can be achieved with all those objects & planes but you’d think at least some optimisation work could be done on them to improve performance. I believe iniscene are realising a Heathrow soon, looks much more ‘premium’ but i hope it’s been well optimised. Would be great if it is better on performance.
I agree that taxiway, gate/ramp signage needs to be improved at all airports. It becomes a guessing game without the taxi ribbon (that also needs options for size and colour) to know where you are going. Also, make some of the signs larger or font larger as they are hard to read with the few we have.
LEMD is also a disaster, not a single gate is placed in the correct place in the satellite terminal T4S.
I imagine they were in a rush to release the game, airports since Japan update have been way better.
Overall, some of the “handcrafted” versions aren’t as good as several payware but oh well. They basically cost like 2-3 dollars extra when you paid for the premium or premium deluxe. Then again…there is payware that is over 20 dollars that looks worse…or not worth 20 bucks.
Example: there is freeware on flightsim.to that looks fairly good compared to 20+ dollar payware scenery. Granted, the payware does look better but for 20 some dollars? Meh.
Yeah, I have noticed JFK and LAX are notorious. Even KBUR area is bad. That is with or without 3rd party scenery but with photogrammetry (spelling?) turned on. London City airport as well…
I think the ‘handcrafted’ airports ARE disappointing as are some of the ’bonus’ default planes I got with Premium Deluxe. You can try to analyse the breakdown of equivalent costs all day to try to justify the standard but that doesn’t excuse a poor product. I didn’t set the price, I merely PAID it. What exacerbates the situation is that they remain, despite 2 years of opportunity to rectify, broken / unfinished.
I’d rather they’d made less airports and aircraft and done them well, than give us a higher number of relatively half-@rsed content. The default, un-modded, 787 is a complete waste of time.
A lot of handcrafted airports have been crashing the sim as of late. DFW and SIN are 2 main ones that have given issues for MONTHS. Seems like another issue that plagued the Potomac region for a bit of time before they got around to fixing it.
I was just reading your other post on the issue.
I personally have no issue flying into JFK, LAX or DFW.
These are all high density scenery areas.
That almost seems like a streaming issue.
The first thing coming to mind is the Window’s download limiter.
Nope it’s not that I checked that to be sure. I don’t have a limit in place. That was the first thing I did when I got my pc was to make sure that limiter was off.
I’ve noticed a bunch of payware airports I’ve purchased, especially those from MsfScenery or whatever they are called, use very poor VFS naming procedures, such as modellib.bgl files and other common names on common paths. This can cause crashes as the VFS gets confused about which files to call. I have to go through all my downloads and fix filenames and paths all the time.