PNW.002 patch for NA BLUE Pacific Northwest is now available!

John,

How do you find the exploding artillery on Fort Lewis? Also, didn't find any military vehicles, am I doing something wrong?

Matt
 
Download the pdf file, which is available now:
- http://orbxsystems.com/forums/index.php?topic=23870.0
and you'll find this:
"Military vehicles and personell at Fort Lewis Military Reserve (south of KTCM and at KZ10) including shell blast effects at the artillery range N47°0.93' W122°35.90' every day between 11AM and noon"

Greetings
Dieter
 
kdl said:
Download the pdf file, which is available now:
- http://orbxsystems.com/forums/index.php?topic=23870.0
and you'll find this:
"Military vehicles and personell at Fort Lewis Military Reserve (south of KTCM and at KZ10) including shell blast effects at the artillery range N47°0.93' W122°35.90' every day between 11AM and noon"

Greetings
Dieter
Click to expand...
Thanks Dieter, just glossed over that fact because I was too elated to have movement represented in our backyard, including things going boom!

Matt
 
Stryker,
Yep, just set the sim to "day" and you'll see it. Roughly the size of a 155 going off with a flash and dust cloud. Pretty neat stuff. There are at least two HMMWV's and an old-style 5-ton (Not a FMTV) on Salinas DZ with a TOC set-up just across the hardball from them, right where you'd split off of the "Y" in the road to go to OP's 8 & 9.

Call me picky, but I wish there was a way to get rid of the Orbx static gray Blackhawks and B-52's and replace them with 47's, 58's and OD green 60's.
 
NWarty said:
Stryker,
Yep, just set the sim to "day" and you'll see it. Roughly the size of a 155 going off with a flash and dust cloud. Pretty neat stuff. There are at least two HMMWV's and an old-style 5-ton (Not a FMTV) on Salinas DZ with a TOC set-up just across the hardball from them, right where you'd split off of the "Y" in the road to go to OP's 8 & 9.

Call me picky, but I wish there was a way to get rid of the Orbx static gray Blackhawks and B-52's and replace them with 47's, 58's and OD green 60's.
Click to expand...

LOL, you too have seen the B52 sitting on Gray AAF then? The biggest birds to fly into GAAF are just C-17s and they are impressive when they grace our presence. Since purchasing Helitraffic 2009 from Flight1, it provides the option to add much more heli traffic from GAAF then was present before. It also allows you to scour your available copters within your flyable and AI databases.

Matt
 
strykerpsg said:
LOL, you too have seen the B52 sitting on Gray AAF then? The biggest birds to fly into GAAF are just C-17s and they are impressive when they grace our presence. Since purchasing Helitraffic 2009 from Flight1, it provides the option to add much more heli traffic from GAAF then was present before. It also allows you to scour your available copters within your flyable and AI databases.

Matt
Click to expand...

Matt,
This patch is really strange since it's not accurate at all for aircraft at JBLM. Seems like they took the six B-52's in the original .bgl and cut them down to just two and moved them to where 66th AV is currently stationed in real life. Weird and I still don't understand why they're there as there hasn't been a B-52 stationed in Washington State since the 1990's (Fairchild AFB in Spokane).

If they wanted to do it correctly, you'd have Chinooks, Blackhawks and a C-12 on the north end of the field (66th Aviation, WAARNG), Kiowa's for the CAV squadron on the east side, and Chinooks/Blackhawks for the Medevac units near the tower. Possibly another C-12 and Citation for the I Corps Staff.

Cool to know about the helo traffic. Maybe I'll hop on over to the Orbx forums to see if they can help me with an exclude file.

Heck, I wouldn't mind a bit if Orbx asked me for some help since I'm a stones throw away and a military member.
 
Task Force 160 is also a permanent party unit on GAAF now too. They have a plethora of MH47's, MH60's and the occasional MH/AH6 Little Birds, not to mention lots of MC-130's and the occasional AC-130, but no B52's. It's just too short of a field for them.
 
The patch has totally made FTX unusable. I can't even get a clean install know I must have done something bad :kilroy:

Clean install wants to load on my decktop in a "new folder" and it creates just that
 
doublecool said:
The patch has totally made FTX unusable. I can't even get a clean install know I must have done something bad :kilroy:

Clean install wants to load on my decktop in a "new folder" and it creates just that
Click to expand...

I've answered your support query on our forums and offered a suggestion. The issues you're having are totally unrelated to PNW or the patch, but rather something has gone amiss with your FSX registry entry.
 
I removed PNW as per Orbx Forum
I used the "Registry Utility for FSX" from the Orbx forum Site Pointed to me by "koorby" and it fixed the registry issue I was having

I reloaded PNW,,, once it loads it opens FX Central Check North America...start fx,,,close fx and then run update 002

That is what I did
Took about 30 mins

also the free ware and the two payware airports worked fine...so far

Hope this helps
 
doublecool said:
I removed PNW as per Orbx Forum
I used the "Registry Utility for FSX" from the Orbx forum Site Pointed to me by "koorby" and it fixed the registry issue I was having

I reloaded PNW,,, once it loads it opens FX Central Check North America...start fx,,,close fx and then run update 002

That is what I did
Took about 30 mins

also the free ware and the two payware airports worked fine...so far

Hope this helps
Click to expand...

I didn't have the same problem as my registry is fine. It's the error messages I get during loading the patch that are my issues.
 
Well I backed up and deleted all the offending .off and .bgl files and now Darrington looks like this...with some really interesting mini-cliffs...

Darringtonafterpatch.jpg


Darringtonafterpatch-2.jpg
 
Roger said:
Frankly this is poor service. I am definately not amused!
Click to expand...

Roger, you did not log a seperate support post on our forums for this issue. I've actually created a small patch .exe which will fix your problem, and I see that you 'tagged' your issue onto Ray's original problem report which was marked [RESOLVED] on our forums as per our usual MO when an OP's issue is resolved.

If you bury a support issue into someone else's thread, then yes, expect us to perhaps overlook it. I will now go back to our forums and provide the solution to you.

In future, may I request the following simple courtesy:

- You post a seperate issue pertaining to your specific problem on our support forums as the OP
- You don't post here on SOH and other forums bashing Orbx for lousy service. That's not kosher :(

Frankly I am the one who has the right to feel disappointed that you're airing dirty laundry at SOH when we provide world-class service on our own product support forums. You surely cannot expect us to trawl through all the FS forums trying to resolve FTX product issues when they are reported there?
 
John,
I find your forums confusing and you do visit here regularly. This thread here at the SOH was started by Jaykae and as such is a ORBX thread, is it not?
I have had this issue since patch release date and in this thread you said you would help and I gave you a shortcut to the thread I'd posted in. You didn't respond.
So I attampted to solve the issue myself resulting in a total wreak of Darrington which is my favorite place to visit in PNW, hence I was not amused.
I have never slated your product which is excellent, just the handling of issues.
Lastly you clearly don't understand the first rule of salesmanship and by slagging me off I would bet you've done far more damage to ORBX than I had in my comment.

Now if we need to continue this conversation I suggest we go to pms and I would strongly suggest that this thread is closed.
 
PNW Problems

John, I had the same problem as Roger but followed your procedure of removing PNW and doing the reinstall. I have to go with Roger here. When a guy can no longer fly in his favorite place and help is delayed from misunderstandings, one gets frustrated.

My suggestion is this, handle the problem with PM and email to get the situation resolved. The personal touch goes a long way to making things right.

Jon over at VRS and the Super Bug has the ability to take care of people and problems like I have not seen for years. His personal touch solves many problems caused by the diversity of these darn machines.

Hope Roger gets things cleared up and for what it is worth, your products John are outstanding.
 
Roger's problem has been resolved, as have most issues logged by our customers on our forums. We provide what I believe to be the best support in the industry on our support forums. I also don't mind helping people out via PMs and email, even though that's not our usual support path.

What I get irate about is people posting about "bad service" on other forums when they have not yet taken advantage of our support infrastructure on our official support forums. To me, that's harming our reputation before giving us the chance to resolve their issues.

Also, we all live in different timezones, and sometimes an answer can take 12 hours or more. Compare that to many other vendors where support questions can be completely unanswered for days or weeks, or in some case, never.

So please cut us a bit of slack here folks. We have an official channel, so use it.
 
You must log in or register to reply here.
Back
Top