Joe L

I live in Rio Rancho - same here, as it was when I lived in Santa Fe many years ago. Tragedies do happen, in 2005 a baby being held in someone's arms outside in their driveway was struck in the head by a stray bullet on 4th of July. She survived, but it was touch and go.

It seems to be just the right speaker now, but, that seems better... thx

I discussed nothing via any support ticket, I just purchased and downloaded 2-3 hours before my first post on the issue? With what I downloaded from your site today the left - right channels are not correct - as indicated by the audio test. The FO is not centered it is definitively coming from the left chanel, and the captain the right. The FA Calls also come through the right. Again, this is happening only with the Airbus. I verified channels are playing correctly on the NGXu and now the 747 as well (where the FO does seem to sound centered).

Should add - using button control.

Just purchased and installed the Airbus version. When playing the audio test the left and right channels are reversed. It sounds as if that is the case with the voice audio as well when FO is speaking. I have only the Aerosoft A330 installed, no other AS Airbuses. This is unique to the Airbus version. I have verified my system audio is correctly configured. I also tested the FS2Crew Audio in the NGXu and the audio test / general audio plays correctly through left / right speakers. Thanks for any help. Joe

+1

I don't see exactly the same issue, but, those "saw tooth textures" are the silt lines and although not shown in detail you can even see them on the ORBX product page. (Left column of screenshots, 5th row). I had not noticed it before, but mine looks quite similar to yours in that area with rough edges in areas. I did a quick web search of other PAVD shots and interestingly it is much less pronounced in most screenshots. I normally do not get the oval you mentioned, but,when I paused by sim I do see something similar but it does not follow me and eventually goes away. I also often very briefly see square lines in the textures that go away as the texture loads.

I am not overly pleased with price point and how that may equate for 64 bit. I also am disappointed by the whole navigation data choice. Too bad - so sad for me. I *hope* the Challenger is not past this in terms of price point - I honestly look to that as what I would potentially buy (probably the -X as well...). I do hope it is successful for EagleSoft despite my consternation.

Price is even higher if it reads correctly. Uses a different nav data source - RealNav which is $40 per year for quarterly updates if you are a "home user". Poor effort at screenshots - no actual clear shot of displays in action so far.

705 GB (323 of that is ORBX), plus at least 165 GB in other folders / drives (P3D Add-On folders, etc etc).

Do you use FSAerodata? I experienced a similar issue between HF1 and HF2 with a different airport from ORBX. Moving the FSAerodata folders below any add-on airports solved it for me. Just a thought . . .

Have you verified that you have the file AFX_TNCA_ALT.bgl in ...\Scenery\World\Scenery ? I have been on P3Dv4 for awhile, but, that is what I see, so just pointing it out as a possibility. Good luck.

The other dll might be MV_WX.dll which is in the MilViz AC panel folders and the main gauges folder for me.

I asked this question on on previous version and was told "Normal behaviour. The module only does something if the developer uses the API. Otherwise it just occupies RAM, waiting for instructions." https://www.realenvironmentxtreme.com/forums/index.php?/topic/49785-flysimware-lj35a-and-wx-radar-solved/&tab=comments#comment-311044 Curious if anything has changed . . .

I believe it may be solved - at least for the DME Ident part. I still have the ADF Ident button moving in and out on its own. Need to do more testing, but, that looks like it happens mainly when I use the audio panel on the GTN, which can easily be avoided. I was using the GTN Trainer 6.50, which apparently caused issues. Went to 6.50.1. So far a quick test looks like it may have helped. But, I need to check my GTN version (F1 2.09), I have no DME or ADF buttons in my audio panel . . . No controls set to the ID buttons, checked that first. Thanks to both of you for your input.

P3D4.4, should have added that. I will try with the F-35. Have tried with the default F-22 and the Mooney analog. Both starting with that AC and loading then switching, and, setting the AC as default but loading Falcon in set up. Thanks for the input !

I have a situation where the DME Ident buttons are struck "on" in the Falcon. This causes the annoying loud Morse code beeps. I have tried to be sure I am starting in a default AC, and, all ident buttons are off. The buttons become depressed "on" as soon as I turn on the avionics, and, even if I press to turn off (lower left side panel) the buttons will turn back on within a second or two. What is odd is it seems to change in various phases of flight. I may be able to turn off, but seems always on during departure and arrival. Anybody have any ideas? This is driving me nuts.

Even at 0.80 mach the time looks off at 6:22 unless there was zero wind.

Upgraded to 1.8, uninstalled first. I see a couple of issues - first - all windows are now opaque in the external view. Second, pulse lights no longer visible in external view (full landing appears ok). The area in front of the lights appears opaque. Both pulse and landing lights show on ground, but, do not illuminate the ground and are just white splotches. Third, at night when on the cabin lighting bleeds through the external view and lights parts of the middle intake and wing. Tried several default repaints - all the ones I tried exhibited same behavior. I find the new repeat rates on the strobes and beacons to be way too fast, but, that could be true to life. I am getting 2 flashes a second with no gaps. May be unique to my system, any input appreciated.

I have my tolerance set to 10,500, which is where I was flying at, although with a corrected altimeter. If that is what happened there was no "heavy breathing", no screen going black per the manual.

I did experience something similar while at cruise. Cruising along 30-45 minutes into a flight and all off a sudden hard bank and uncontrollable, no recovery. Engines had been fine, was at 10,500 cruising well below yellow. Even as it was going out of control input seemed to have no effect, both engines appeared fine and all gauges indicated they were performing equally even as it tumbled into the ground.

Santiago - thanks again for sharing - much appreciated. Joe

Nice post ! Would love to have your PFPX profile. Joe

OK - never mind - found it in my Users/Public/Desktop folder - fyi not a convenient location. Liking everything so far.

Is the GPS switching tool available? I do not see any options to change inside or outside the sim?