Just finishing up the orthos now. AFS 9-11 are Level 15; AFS 12-15 are Level 20. And it is beautiful Far better than what MSFS has offered for my area. And much more realistic, too. The canyons in SW Idaho are not to be missed! I'll have some spawn points there to help you find it. I've lived here more than 20 years and I never knew how amazing that corner of the state was until I started this project.
But, there is still MUCH work to be done on cultivation and object generation. And I want to add things like backcountry airports, as well as a few spawn points like dry lake beds and random off-airport helipads. This scenery will play nicely with airplanes, but it's really being designed as a helicopter playground first and foremost.
This project originally started as a supplement to my IRL pilot training, so absolute accuracy of airports with the appropriate lighting was considered mandatory from day one. Since that time it has grown into the most detailed representation of Idaho that I could possibly create.
This scenery package is HUGE. Roughly 100 GB, at this time. So sharing is going to be the next hurdle to conquer. The realism of training was first and foremost for me. Everything else came second.
My IRL flying is taking up most of my time right now, so I don't have a forecast of when this will be finished. And the work that remains is the painstaking stuff that I must do my hand. My computer has done just about all of the "auto-pilot" work that it can, so the rest is up to me.
After looking at this Oahu scenery addon, plus the fact that FS2 now has 2x heli's, I decided to buy/try this again (not even on a Steam sale, lol!). After a full day of flying a R22 around Oahu I gotta say I'm very glad I gave FS2 another go.
The AFS2 R22 is the most accurate R22 I've found in any sim. It's not perfect, but it's better than all the rest.
There are two other freeware Heli's available on this forum. An AH-64, and a Lynx. Both by larrylynx
Has anyone ever used Google Drive to distribute scenery? My scenery files are simply going to be too big for the file limits of this forum, and that of flight-sim.org. I'm looking for alternative solutions.
Alternatively, I could just host a website and post them there if there are no restrictions to the links that can be post here, and on flight-sim.org. I'd really like the scenery to be part of the map over at flight-sim.org, but again. It will never fit within their limits.
Here's some teaser shots of what I'm working on for the State of Idaho.
I'm thinking there's no reason to use Zoom Level 20 for AFS 9-11. And reducing the zoom would also reduce the additional size.
My current thinking is that I'll just host the files on my own web server, or via Google Drive. Would there be any problem posting links to either of those locations cause any problems here, or on flight-sim.org?
McCall will be included in Region 3, which is the first region to be released. But the download is going to be huge. As it stands now, all of Region 3 will be over 100 GB on my end. How I get that downsized to something manageable, without sacrificing quality, is the big question right now. But the detail is going to be worth it. Since I live and fly here (Region 3), I'm obsessing over every detail and making it as accurate as I am able to.
All ortho's are Level 20 zoom. Right now, only AFS 12-15. I hope to be able to add AFS 9-11, but as mentioned above, size is already a problem. For size comparison, a single install of MSFS is about 91 GB for the entire planet. This will be larger than that, at least on my end, for just Region 3. Here's a screenshot of KEUL at dusk. Caldwell Industrial Airport at dusk
Also, there's zero chance of it making it out by Christmas. Probably sometime around MAR-APR would be my best guess.
I know when they are activated as I have the freely available Operators Manual for the AH64A. It would be nice to get the correct sounding warnings but I may have to get creative
I know that it's "Bitchin' Betty" as voiced by Erica Lane, if that helps at all. But I wasn't able to find any examples this morning.
K9NSP: Please post more details and if possible tell us the folder where the scenery is installed and the TSC file as well.
It's all airports without an ICAO, but we'll stick with the S78 example in Idaho for now.
Path to S78 is C:\Users\order\OneDrive\Documents\Aerofly FS 2\addons\scenery\k9nsp_Idaho\airports\Region 3\S78
TSC for S78 is attached.
The one exception to the above statement is the OXBO airport. Also non-ICAO, but it does show up as being available.
Path to OXBO is C:\Users\order\OneDrive\Documents\Aerofly FS 2\addons\scenery\k9nsp_Idaho\airports\Region 2\OXBO
TSC for OXBO is attached.
Where exactly is this? Can you show us the coords?
Actually, the reason I can't find it may have to do with the fact that I've updated elevation mesh since that photo was taken. It may not be a problem anymore. And it may have never been an IPACS problem. I'll take better notes should it happen again in the future, but I wouldn't lose any sleep over that picture above. It's from custom scenery that is very much still being developed.
Where exactly is this? Can you show us the coords?
I thought I knew exactly where this was, but I can't find it this morning. It may be that I'm lost, or it may be that it only happens in VR and/or the helicopter because I'm just zipping by in the F-18 this morning (without VR). I don't have the time to dig deep with the helicopter this morning. But I'll try and find it at a later date and get back to you.
But custom scenery and elevation is involved. So it may not even be an IPACS problem. I simply don't know yet.
The Google resolution in the Fork Salmon River area (44.97570 -114.73509 ) is fantastic!
We are all looking forward when K9NSP will have ready this whole area.
Region 3 might make it out in time for Christmas. Region 2 has problems, and the others haven't even been started. But I will be offering a beta preview of the KEUL airport in the not too distant future.
I found some floating trees today. It's right at the edge of the scenery I'm creating for Idaho. You can see my scenery in the foreground, and the AFS2 default scenery in the background. The trees are floating in the AFS2 default scenery.
I've not yet made any effort to determine if my scenery is causing this, or not. This is the only place that I've seen any anomaly's, and I've been working on this package for months.
I am working on an elevation mesh for Idaho (nearly ready) on a basis of 10m 3DEP data.
Are you interested K9NSP?
I might be. I'm currently using 1/3 arc-second DEM and I'm not sure how that compares. But if it's better it's definitely worth it to repackage it for my scenery.
Also, those Hawaiian Islands look great. I'll have to give those a spin sometime.
Region 3 (Green) will be done first, with Region 2 (Yellow) expected to roll out after that. The trailer above is from Owyhee County in the Southwestern most corner of the state.
With the release of MSFS, this is becoming unlikely. AFS2 can't be a MSFS competitor. AFS2 will become a niche product, so the question is, on what niche do they focus.
Nah. MSFS is full of problems; it lacks VR, and while the world is there, it's not terribly accurate. It's just autogen, for the most part. And no helicopters. I heavily prefer AFS2 to MSFS, and I do own them both. I'm still making my own scenery pack for Idaho for AFS2 because it's noticeably missing, and the MSFS version doesn't even remotely look right. MSFS has the area all green and covered with trees, and that's just not what it looks like.
If you prefer MSFS, Happy Trails...
Please explain the process that you do to get the error. Are you running the latest version of Aerofly FS2 and Steam?
A recent update to Steam seems to have fixed it. I no longer get the error if I open with Steam; and I can once again open directly from the Oculus Library in VR. So, for me, it's all good.