The website and forum will be intermittently unavailable while we're making some security updates.
File uploads to the download hangar are also disabled until further notice.
Joseph29 wrote: ↑06 Feb 2017, 03:41
Is it possible you can fix the parking spaces for the E-2 Hawkeyes? The parking spots are to close to each other and the wing tips are overlapping each other.
This screenshot shows the designated parking spots for the E-2s of VX-20.
There are no overlapping wing tips in these parking positions.
Joseph29 wrote: ↑06 Feb 2017, 03:41
Also would the USNTPS C-12's and the USN Air Operations Department C-12's have the same parking codes? Both of them was included in the original Patuxent River but only the USNTPS is in the parking code list.
The USNTPS C-12s need their parking code changed to NTP2. (should be 6 aircraft)
The other C-12s of the original Patuxent River package keep their original parking codes (VXS1, VX20, 7A - two each).
This is why they are not listed in the chart on page 34 of the manual.
And that is probably why I forgot to add them to the parking code overview.
Hartwig, I check BuNos for those special C-12s and I'm showing they are all gone, so no parking needed. I haven't made many changes yet for the FSX install (wanted to see Martin's), but a quick flyby showed correct parking and tons of cool traffic!
Ok I see what happened, the Hawkeyes I saw were ones visiting from Norfolk. They were parking where the P-8's are parked. And those wingtips were overlapping (If I knew how to do a screenshot I would show you). Also thanks for the explanation of the C-12 parking codes. I changed ALL of them to ntp2.
Fantastic up-date, well done to all concerned. Only problem I have come across is that I have no v22 Ospreys! Added textures & cfg details to USMC V22's but see nothing at Patuxent River!! Just me or anyone else?
Dave
merlin101 wrote: ↑08 Feb 2017, 20:52
Fantastic up-date, well done to all concerned. Only problem I have come across is that I have no v22 Ospreys! Added textures & cfg details to USMC V22's but see nothing at Patuxent River!! Just me or anyone else?
Dave
Thank you Dave.
Did you renumber the aircraft.cfg entries?
merlin101 wrote: ↑08 Feb 2017, 20:52
Fantastic up-date, well done to all concerned. Only problem I have come across is that I have no v22 Ospreys! Added textures & cfg details to USMC V22's but see nothing at Patuxent River!! Just me or anyone else?
Dave
Thank you Dave.
Did you renumber the aircraft.cfg entries?
I just checked out the PAX4 afcad on my system and they are there no problem.
Now I have to say that I do integrate everything released into my system rather than just copy everything across so it could be that I fixed an error but these were an easy cutover.
It is not something as simple as the Traffic_PaxRiver_HX21_MV-22.bgl not being in your system is it?
Steve _______________________________________________________
Quid Si Coelum Ruat _______________________________________________________
Have that traffic file installed, opened it using ttools just to check, All other files work perfect! re-check V22 a/c file & that appears fine. I've added the textures & cfg details to the JYAI v-22 osprey USMC USA file, all numbered in sequence. Going to deleted them & re-install later! Quite sure it's my set up as no one else seems to have the problem! Will persevere!!
Dave
Where can I find the traffic file Traffic_USNTPS_Superhornets.bgl? I was at Patuxent River earlier and noticed there was no F-18F's. I downloaded the package again and read the manual, and it said this "Aaron Haase created a small package representing the three F/A-18F Super Hornets of the US Naval Test Pilot School." But I can not find the traffic file or the paints.
The last component of the upcoming F-35B package to be completed and most definitely worth waiting for. Like Brent's Iwakuni AB, Japan, Hartwig's Patuxant River just makes for a really interesting scenario and show case for the F-35B and for others aircraft there too. I've been playing with it for a week or so now and I have fun every time I go there.
The scenery is for FS9, but the files necessary to enable it to work in FSX and P3Dv4 are in the F-35B zip ready for a simultaneous release when Hartwig is ready with his package.
I know it's taken a lot of design work and tedious testing. Well done Hartwig and many thanks.
For the FSX and P3d crowd, does this scenery make use of Microsoft’s built in Carrier code for the Catapult and AARG? That would be the cherry on top with this package!