An unfamiliar developer Cloudberry Sim has released KOAK Int'l Airport for P3D.  I'd be interested knowing how the looks and performs.

 

https://secure.simmarket.com/cloudberry-sim-oakland-international-airport.phtml

I noticed this released this morning. Interested if anyone has tried it out yet. The price is not bad for what appears to be a better than default airport with some nicely added details. Don't get me wrong, any enhancement to a default airport is a plus to me. It's a large download, 1.1gb. That's close to high end scenery size. From looking at the initial pictures, the grass is very green for the area, probably photo real texture. I would definitely be turning that off so Orbx would mesh better. I do like the buildings and hanagers.

Wasn't there another KOAK in works? 

Anyways, looking forward to the reviews. 😀

Edited August 5, 20196 yr by TalonMX

The list of features are impressive for that price.  

Neither their webpage nor their Support email work at this time.  Seeing as how we just had in this forum another addon recently released that went... well, less than smooth   ... I'll be waiting before buying this one.  Hope it's good... would very much like a nice KOAK.

Greg

Here is the FSElite article on Cloudberry Sim KOAK development back in March.

https://fselite.net/previews/cloudberry-sim-announce-oakland-international-airport/?fbclid=IwAR3Ut3ihYwzqTPgnkFGV-8FTr-TnmxpTVv7V-UWZu50vsxb0Zu_KxsYhYzo

Actual postings from the Developer. 

https://www.fsdeveloper.com/forum/threads/oakland-international-airport.444892/

Edited August 5, 20196 yr by TalonMX

I purchased it last night.  It's not bad, but there are a couple of issues.  It comes with static jetways, but it also comes with a GSX ini file.  The big issue is trying to get it to work with FTX NoCal.  There airport is there, but all the taxiway and parking lines are missing.  There is some conflict with the FTX files.

So this is another misfire?  I currently have something from Photo-Real that is a basic ADE based design.  Lot's of cargo goes through KOAK.  Hope this works out.

pads103

Do you have FTX Vectors?  Have you tried using the AEC function in vectors?

I am pondering about this, too. The default KOAK isn't that exciting. 

The first things ORBX suggests in such cases are (i) use the Vector AEC tool, as Paul mentions, (ii) search for all files containg "KOAK" in the several ORBX NCA directories and rename them from .bgl to .bgl.off (usally there are three of them).

If this doesn't help, one could ask in the ORBX compatibility forum for NCA.

Kind regards, Michael

All - yes, I've tried the AEC in vector.  It didn't work.  There were three conflicting files in the NCA scenery folder for KOAK which I renamed to off - this corrected some issues, but not the taxi lines.  There is something in the CVX folder that is causing the conflict - could be one of the wetlands files - haven't had time to verify yet.  The developer noted in the manual that the scenery is not compatible with FTX NCA.  Too bad because it's nicely done.

43 minutes ago, pads103 said:

 The developer noted in the manual that the scenery is not compatible with FTX NCA.  Too bad because it's nicely done.

Thanks for the hint. This will exclude 80% of the potential users. Hard to understand such design decisions.

Kind regards, Michael

5 hours ago, pads103 said:

The developer noted in the manual that the scenery is not compatible with FTX NCA.  Too bad because it's nicely done.

pads103

Have you tried it with FTX NCA disabled.  I know if compromises the level of scenery detail.  I'm curious as to whether it solved your problems taxi lines?

Well...I was able to isolate the file...it's the SF Water file in the CVX folder.  Without that file, the bay becomes a desert.  Oh well, guess we'll have to live without taxi lines

Completely agree Michael. I would love to have another SWA destination.

5 hours ago, pmb said:

Thanks for the hint. This will exclude 80% of the potential users. Hard to understand such design decisions.

Kind regards, Michael

Yeah seems questionable to to design an airport in that area without NCA compatibility in mind, oh well.