iniBuilds

Hello! 🙂 https://store.inibuilds.com/products/inibuilds-new-york-john-f-kennedy-kjfk-msfs We announced today the scenery will be released on Friday for 19.99 GBP Some content creator's and media have it now pre-release.

We wanted to come on here and really thank you all for the amazing and lovely comments. We are going to do our best to continue making fantastic products, both providing the best quality and variety. Thank you for the support - your feedback and support is what keeps us going and motivated in making more content!

Hello, To give those concerned an update on progress... Hopefully this will address the most-mentioned issues for the time being as the first update. The full changelog is below: Upcoming Changelog: iniScene EGLL MSFS V1.10 - AI traffic bugs resolved - Added T5 night lighting emissive texture - Adjusted some T4 emissive textures - Adjusted red brick texture - Improved T5C textures and fixed accessory building roof to be correct. - Added more lights to T5B/C - Added more dirt on stands - Added Runway Guard lights (wig-wags) to runway/taxiway intersections around airfield This update is available via iniManager for iniBuilds Store customers immediately and SimMarket to come soon.

HI @DaWu, Thanks for your question. Simply to put, we have no control over their satellite imagery, so we're forced to use our own if we want to make changes or a higher-resolution image than what's available. Custom satellite imagery is still part of the process for any high quality scenery in MSFS, the quality and tangibility of it won't suffice to our needs, since we don't have control over removing lines, windsocks, aircraft on aprons and lines and so on and so forth with the in-sim bing data. From a developer's perspective and for an end result of a major payware development, it just isn't good enough by default. This also factors in the fact that there are users who don't use the Bing Imagery streaming, and the airport will look strange for them when not paired with a satellite image it was designed for. Thank you.

Hello, I think the feelings for Heathrow are rather mixed, but also some statements are being taken out of context and assumptions being made. Firstly, to address the size "issue". Heathrow has been heavily optimized from the ground up - each and every building, GSE model, car, and you name it, has had a set of level of detail models created for them or also known as "LOD". This helps with performance greatly when you're further away from a model by not taking up so much system resources by decreasing the level of detail as you're further away with lower-detailed models which also in addition to that feature a few levels of decreased texture size and so on and so forth. This results in over 2x the size of what you're suggesting @superspud. https://docs.flightsimulator.com/html/index.htm#t=Asset_Creation%2F3D_Models%2FLoDs.htm&rhsearch=LOD&rhhlterm=LOD There are in addition to this, 7GB of compiled textures, all full PBR. But don't think we've skimped on this, many textures and materials are re-used throughout the airport, but if we wanted a diverse and whole, non-repetitive looking airport. The textures are also all optimized as per SDK standards and aren't loaded the further you are away from a specific object due to the lowest-res LOD only loading colours and not textures, again for performance reasons as prescribed in the SDK. And finally, there's the satellite imagery, which spans outside of the airport boundary itself. This as a source file is over 10GB in size and when compiled by the sim it is 1.84GB with multiple LOD levels inside also to allow the sim to load lower-res versions of the imagery further away. The 10GB size for this airport is inevitable, and we can only see it getting bigger with future updates as there aren't many further optimizations that can be carried out on this scenery. We are constantly monitoring the community for feedback and take onboard what's actively being fed to us. We hear you, and we're implementing what we can to make this the best and most-preferred Heathrow add-on for MSFS. In addition, we've paused development on all other scenery projects to resolve Heathrow feedback ASAP. Currently we're acting on the following; - Night lighting improvements throughout - Terminal lighting improvements at T5 - VGDS solution (longer term implementation) - Increasing dirt at stands - Adding airport side roads - Increasing cars on landsides for added immersion - And fixing numerous bugs reported to us on our own forum and support tickets as well as what's been picked up throughout the wider community. In response to some other comments: Please do elaborate, this seems rather vague of a statement based on other individuals' disgruntlements. We'd love to hear your thoughts on the "garbage" aspects of the scenery, so we can strive to improve for future updates. We will be continuing our entry into the scenery market with many more releases planned to come throughout the year through iniScene. I can wholeheartedly assure you a lot of love, sweat and maybe even tears went into the development process of EGLL. We're completely open to feedback and implementing it as mentioned further above as this is a passion project for many on the team, and we want to see it do its best out there. But with an airport of this calibre, there has to be a limit on the level of detail we go down to solely for the purpose of guaranteed performance and it being as best as it can. As mentioned earlier in this thread, we've optimized this scenery very well in-line with the MSFS SDK guidelines in hope to have it running smoothly on the minimum specced MSFS PC. The comparisons raised in the community are rather unjust, and we understand expectations may have been higher, but for an airport so large, we sadly couldn't go to the level others have without having a different side of issues. Thank you.