It took a long time of a very dedicated and and extremely hard work to develop this and your support is truly appreciated!
I would love to encourage feedback on this scenery, so any issues are addressed and possible improvements are released in an upcoming update, which will also feature detailed Ottawa Flying Club buildings and Sander Geophysics hangar for the GA area, animated people around the terminal and more airport buildings.
Done and extremely well done as far as the airport is concerned. As I said in my review, your airport is well worth the money and compares favorably to products by Drzewiecki Design and Aerosoft. Highly recommend. The pictures really say it all. Great attention to detail and I love the main terminal modelling. My only nitpick would be that the ramp markings look a bit too fresh. For those thinking this isn’t a “Must Buy” because it is Ottawa, United Airlines offers CRJ service from both Washington-Reagan National and Washington Dulles. Pairing this airport with Drzewiecki Design’s Washington D.C. scenery and Reagan National Airport makes for a highly immersive experience. Calling @FilbertFlies–I suspect that you will want to do a proper review of this airport.
Thanks! Glad to hear that. I will actively contact reviewers after I release the update so the full experience is reviewed. But I won’t say no to early or preliminary reviews.
Ramp markings and painted lines are a challenge: not because I can’t make them faded enough, but because some lines and hatched areas (yes, red ones) are not possible to replace with my own materials. So my markings and lines have to coexist with default ones, and can’t be too different. So there is some fading and wear on the lines, markings and runway markings, but not too much to make them stand out. For instance, I have reworked and manually places all runway markings wiht a striped and slightly faded realistic markings with some rubber marks on them. However the numbers are still default and generated by the sim. so the markings can’t be a lot dimmer. Also, it was a long battle I almost lost, to get the lines wiht black borders crisp enough without too many artifacts: MSFS heavily downsamples ground marking textures (that’s why they are always blurry, no matter how large the source texture is), so I was getting huge problems with square blobs of black mud on my lnes as downsampling artifacts. There needs to be sufficient contrast to avoid those. Anyway, for now I thinkg the markings are a good compromise, all considered.
I had 51 sales so far (in 1.5 days) and no other CTD complaints. But MSFS is prone to CTDs generally. It drove me crazy in development. Editor could CTD when I was just moving around on occasion. So something else can be affecting your particular case. Try moving everything from the Community folder and just leave CYOW there. See if you have a CTD then. If no - the problem is with something else.
There is definitely no CTD in my sim when loading the scenery - I did it many times, obviously. It can CTD when opening Scenery Editor project though, but that’s my pain, not yours
Feel free to contact me in the messenger/chat on my website or through email if you will need more help figuring this out.
Out of 61 people who bought and installed the scenery in 3 days since release, there were 2 people who experienced CTDs and contacted me. Suspecting a conflict from another scenery, I advised them to remove everything but my CYOW from their Community folder for testing - and that has cured the problem in both cases. Then, bringing scenery one by one, as I recommended, one of the two have found the offending scenery.
It appears that there are 3 bridges in Montreal from flightsim.to that cause the sim to CTD in CYOW.
Jacques Cartier Bridge, Montreal
Samuel De Champlain bridge, Montreal
Pont Victoria bridge, Montreal
The comments on all 3 sceneries indicate that these bridges are causing CTD’s anyway without YOW being installed, so the issue is not with my scenery but with some others that are not done correctly and are causing CTDs. If you have other addons based on Google photogrammetry data – those would be suspect too. Google photogrammetry imports have a lot of vertices, and I mean a lot. If not heavily optimized and made with LODs they can overwhelm the sim easily and cause unpredictable issues like CTDs.
So if you encounter these issues - with my or other scenery, consider removing all Google data based sceneries as the prime suspects. It may save you a lot of grieve and time
Thanks for the great scenery… I purchased it and it is better than the SIMADDONS CYOW in some ways… Though there are some things missing and also some little bugs that I have noticed. I am going to explain them here for you. It would be nice if you can fix them in the next update along with the Ottawa Flying Club section. I am personally a member and I love it there…
PAPI lights are located on the RIGHT side of RWY14 and not left (Google earth and real life references).
Fences missing along most of the airport border. It adds a lot realism during landing particularly if you can place them at the end of the runways (end of rwy14, rwy04, rwy22 , rwy07 and rwy 32). Currently only rwy25 has fences and ILS antennas in your scenery and it looks fantastic. That would be great if you add them to all around the airport and other rwys.
Approach light posts should be RED and not YELLOW. (Reference in the previous pictures).
Also, I noticed when I select any runway for departure (not a gate) from world menu, there is a discrepancy between the airport altitude and the scenery, causing the plane to fall from a bit of altitude on the runway… It is most oblivious with smaller planes try the C150 or C172… From the picture you see the plane is not positioned on the runway and it is falling to the runway… it is weird and may cause a plane crash sometimes…