Hmm… That could actually be because there may be a bug in MSFS “collision” materials, I suspect. It’s supposed to make things solid (so you can’t drive through them) but I think it’s buggy. The only solution would be to disable collisions for all materials used for a specific building. And I though I did that but maybe I missed some materials and it still does that. At least I hope that’s what it is, that’s just my suspicion because otherwise, I’d have no idea whatsoever…
I will test and if I can reproduce it, and that fixes the problem, I will do an update…
It’s already been submitted… But I may have to resubmit if the roof taxi bug is a thing and I can fix it. Sometimes MSFS acts so weird, and SDK documentation is very basic…
I was going to comment that you could be running around in circles fixing these elevation bugs outside of CYYJ if the elevation changes again in a future MSFS update.
The better solution would be to have a separate download where we can apply the fixes to these elevation bugs outside of CYYJ, and the main download of CYYJ does not fix these elevation bugs. Then we can download the separate elevation bug fix from you, and overwrite the main CYYJ files (we can download the separate elevation fix from your website, or download it from flightsim.to if you upload it there).
In the future if MSFS fixes these elevation bugs, then the main download of CYYJ will work normally, because it never targeted these elevation bugs. And in the future if these elevation bugs are fixed in MSFS, then we wouldn’t use your separate elevation bug fix to overwrite the CYYJ files anymore.
Otherwise, by not separating this elevation fix into a separate download and lumping the fixes into one homogeneous CYYJ download, your prediction may come true, that “this can backfire later if the elevation changes, then my flat polygons may appear lower or higher”
PS. I saw you included the elevation fixes in 1.1.1 already so I guess it’s too late.
I decided to do this, because by far the most sales (or I hope so if I want to keep doing this) would come from MSFS marketplace, ORBX coming second, and there are no options there to include any additional files. Also, I have to keep the packages consistent, or it becomes a nightmare to manage. I decided that those elevated lakes are so atrocious that the quality of life improvement outweighs possible future problems. If Asobo fixes those issues - let me know, and if my fixes would pose noticeable problems (which may or may not happen) I can release an update, removing those polygons.
I will release another update today, v 1.1.3 that will remove collision flags from all materials used in open hangar objects. I think there’s a bug with the collision flag when instead of only acting as a hard object when you bump into the face with that material, it seems to somehow affect the player anywhere below the object. I can’t explain it, it’s definitely a bug, but it sometimes affects open hangars, so I manually went and removed those flags from all materials there, will need to recompile and repackage everything… again…
The 1.1.3 update is online! The jump to the roof was happening when you were passing under (without touching or being anywhere close!) the roof support beam, which material had a “collision” flag on. Doesn’t make any sense, another MSFS bug… I removed those flags from every single material in all open hangars, not just the roofs as I did before.
I also added a few more terrain fixes for MSFS elevation bugs. I hope you won’t notice any weird “mountain lakes” anymore on approach.
It’s not really my place to make an objective comparison, obviously, I’m biased. Instead, I invite you to open my product page and click through the screenshots - and open a competitor’s screenshots window next to it. I have over 40 screenshots. Compare the same areas and make your own conclusions. One thing I can add is I had three (!) local sources, one of which works at the airport and provided me hundreds of detailed photos of the aprons and areas not publically accessible, which I based my modelling on. That’s on top of my extensive research. I.e. I tracked the Architect company responsible for designing the fire station and based the modelling on their data. And that’s just one example. Aesthetically, you’ll be the judge. You can guess what I think.
Feature-wise, some of the notable differences are:
My scenery has detailed open hangars for GA and business aviation, which add a lot of realism when you start cold and dark inside of the hangar.
Has a functional seaplane dock, where you can start cold and dark
Fixes dozens of the horrible “mountain cliff lakes” - an MSFS bug
Ultimately only you can judge if those aesthetics and functional differences are worth paying your money for.
Yes, I did, because there is a flashing beacon on top of it that’s on the chart - so it’s important for visual navigation. I modelled the beacon - and another one on the other side of the airport. But the second radar (that’s inside and lower) - this is not stock MSFS (as I have an exclusion polygon there). I think this maybe is the PuffinFlight “We Love VFR” NA region? The ratio tower is also not stock MSFS.
I don’t think I can override a conflict with another scenery. You can try rearranging the scenery order so mine comes above, but I’m not sure it will fix it - tell me if it does. I don’t think it will help though, as if two sceneries conflict - both will show. I can override MSFS default scenery, photogrammetry etc. but not another add-on.
I don’t own the SimAddons version. But I think Roman Design’s CYYJ is more detailed, and more current than the SimAddons version, based on the photos shown on the SimAddons website. I have not seen any photos of the SimAddons version where the seaplane docks have been done. But Roman Design’s CYYJ has the seaplane docks.
In addition, there are some small details in Roman’s CYYJ, such as the light blue YYJ signs that hang on the lamp posts on Willingdon Road, which is a road that leads to CYYJ:
You can check out Willingdon Road on Google Maps yourself and see the light blue YYJ signs that hang on the lamp posts: Google Maps. I would be surprised if SimAddons went into details like this.
And oddly enough, SimAddon’s is showing a blue sign for the Departures entrance. But the real life photo of CYYJ from 2018 clearly shows it’s not a blue sign for the Departures entrance. This is explained in more detail here. I can only assume SimAddons is referring to an older version of CYYJ, if the Departure entrance had a blue sign before.
From the photos that I have seen for SimAddons CYYJ, my impression is that Roman’s CYYJ is a bit more detailed, more comprehensive, and especially more current than the SimAddons CYYJ.
Actually, looks like it’s possible to make an exclusion package, but it has to be separate (name like zzz-cyyjexclusion or something similar to be at the end of the list). Maybe I will get to it at some point, I’m exhausted now… Or anyone can do it easily, it’s not connected to my package in any way. If anyone does it and posts somewhere, I can put the link on my product page. That would be nice. Otherwise, maybe I’ll get to it sometime.
Actuall, I just watched a video from PuffinFlight - and they named their scenery “a-puf” specifically so everything else will override it. I have an exclusion polygon there, but it would need an exclusion rectange to override other non-default scenery. So I will do it when/if I do another update. So no separate package would be required. But I will have to re-compile and reupload everything, so I will wait for a while to see if there are other bugs I need to fix first…
Thanks! LOL you got me: I wondered why the last screenshot of my scenery was darker and different size? It took me a moment to realize that the first one is my scenery and the second one is a real photo! But that’s what I was aiming at…
I did model taxis on the real ones - same model and real livery of the local company, just as the Police cruisers have a real livery.
I think it’s $24 CAD. You probably want to contact FSElite and ask them to correct the price. And on your website, you might want clearly label your prices as CAD. On the FSimStudio Discord channel, some people also thought your CYYJ was $24 USD.
This will really lower your sales, if the entire flight sim community thinks your CYYJ is more expensive than it really is.
Thank you for creating this add-on. I use it all the time when flying - ironically not during development, so that’s why I didn’t see the conflict. I will add the exclusion rectangle in my next update, which I will issue soon, after I gather some feedback which can bring out more bugs to address.
I love how We Love VFR brings more immersion and realism to the scenery. I fly exclusively in VR so immersion is everything.
