FlyingAxx

Just to throw my 2 Cent in: When loading those POI don't forget to exclude the pimped airport's folder. Otherwise you'll get them twice in your maps, mostly even at slightly different places (others than the ARP).

Me too! Just landed at Tampa /FL) flying a B737 BBJ1 and my frames dropped down to 2.1 FPM while trying to open the front door and to move the stairway into position. It took me about 30 sec to open the door and the rest did only work after closing FSLTL . Finally I wasn't even able closing MSFS, even when finally using Alt-F4.

I've tried a search, but maybe overlooked a related posting. I've just saw a WIZZAIR flight that should have a routing from East to West (close to EDDH) and that appeared in MSFS as flying from South to North. As a friend of mine told me similar effects while flying NATS my question is whether this behavior is as well the result of stock MSFS' ATC. After switching the Injector to use direct connections, everything looks better, but unfortunately not as often like Flightradar shows the real track. EDIT: Okay, I can confirm that all aircraft being injected while flying along the NATS are appearing correctly, but turning away from their course quite soon. It's looking really strange.

Okay, after trying a lot of different things after posting my question I reverted to the previous version 1.8 in order to get Roland's WX-radar working again. Within only a few seconds the fresh panel.cfg was modified and everything looks nice. For FlySimware Cessna 441 CONQUEST ll, REV1.8 a working solution in the VC looks like this: [VCockpit29] size_mm=512,512 pixel_size=512,512 texture=$RDR150 background_color=0,0,0 gauge00=RolasnRadar!oRadGauge, 90,50,330,250, sweep|beam|icing|starton //gauge00=rxpWX500!RDR,0,0,512,380 //gauge01=ControlPanel!clipboard RADAR, 90,50,330,250 Of course I would be still interested having a working solution for the latest revision of the Conquest even if I can't see other functional changes.

Hello guys, I just updated my FlySimware Cessna 441 CONQUEST ll in FSX to REV1.9 and tried implementing the WX radar as I did it before in the previous version. Unfortunately it doesn't show any reaction. At the moment it looks like this: VCockpit29] size_mm=512,512 pixel_size=512,512 texture=$MV_WXM background_color=0,0,0 gauge00=RolasnRadar!oRadGauge, 90,35,330,270, sweep|beam|icing|starton //gauge00=MV_WX!WX, 0,0,512,361 //gauge00=MV_WX!WX, 90,35,330,270 //gauge01 = CONTROL_PANEL!clipboard RADAR, 90,50,330,250 The gauge still works with PMDG's JS41. It would be nice if someone could help implementing it?

Not far away from Bogotá, south of VOR GIR you can find a pole at N 04° 0.01', W 074° 47.42. I shouldn't forget saying, it's the same with FSG including NEXT mesh. Furthermore, I experienced disturbing peaks (rather cones) in the same area that in most cases disappeared when being really close. Any idea how to get rid of such effects or to smoothen them?

Yes, those peaks don't exist in my FS Genesis and they are looking very much like singularities.

Daniel, As I looked a bit closer to some Pacific Islands at French Polynesia I found out a glitch (I think even two) on both sides of the crest in the vicinity of NTMU.

Hi Daniel, While strolling around that area (at least I think I did) I wasn't able to spot obvious errors. The reason might be that the defective (?) file wasn't loaded and my FS Genesis mesh covers the respective area sufficiently.

Daniel, that's the same I got reported from 7-Zip. When packing it as a single file I get 354CB90B. I'm not sure what state is shown here (does it show the packed or the unpacked CRC?). EDIT: A dull question. I just checked a neighbouring file and the CRC had been the same. Obviously the N40E130.bgl is corrupted somehow.

Thanks a lot you guys! However, while unpacking the Asia files I got a CRC Checksum error on one file. Its N40E130.bgl. I'm not on Torrent and used MediaFire for the download. Even if it seems to be an area I'm non really keen to visite, even virtually, I'm think I should report it... BTW, I did the download twice and a coincidence doesn't seem to be probable for the same embedded file.

For me MakeRunways is out of the question. It has nothing to do with your false alarms. The produced files are build upon a fully transparent procedure and are documented in the file "Runways.txt". Correction: The following statement was wrong! You even could delete (better rename) all files produced by this tool and your T7 would build the required file itself while starting up. You may want to install the original r4.cvs instead. BTW, I'm wondering why PMDG is working with redundant information from different sources anyway. As far as MakeRunways is concerned, the information is produced only based on the present flight sim installation while the AIRACs are fully independent with this respect. Hence, you can be sure having contradictions. Probably you might want to check whether you are struggling with other airports overlaying each other. In this case I recommend a little tool, produced by Jon Masterson and you'll find it here: http://www.scruffyduck.org/simple-airport-scanner/4584282795. It might even happen that add-on developers are changing the default elevation without telling this to the respective FS. This usually requires at least a Stub-file of your airport in the folder ..<main>..\Scenery\World\scenery as long as the designers are following the SDK (which means just overlaying and not replacing the original files).

I can only agree to the last statement of Tom as far as wake turbulences are concerned. I'd opened a Ticket at HiFiSim and got really good support. They produced and offered some Beta versions, got feedback and for me the problem is solved now. However, the recommendation to set the wake influence back to 20% is what I'm doing as well, even after running the updated version. The other weather settings are okay for me. The problem of always generated thunderstorms is solved, but they still appear where I would expect them. ASN is now a great and usable product.

How did you install the new NGX version? Did you just install it over the previous one or did you first remove the forerunner version? For me the "repair" did not work, I had remove the existent version first. There was no error message nor any sign that anything went wrong - with just one exception, the weather radar didn't work.

That's my experience, too. That's why I'm not sure on which side of the interface the best could be done.

Devin, your last hint can be helpful for sure. I've lost sight of this function and I'm afraid I have to search for it...

Meanwhile HiFi got a ticket. Interesting, it seems to be time to find out specific differences in the setup or environment. In order to start with something: I'm flying online just by using a FsHost Client-Server configuration and none of the usual online networks like VATSIM or IVAO. I'm using UT with 100% traffic which is still active when flying with my friends (we're not too many). However I'll make some tests now with locally induced traffic only and I'll look far a busy airport, too (I think London Heathrow is okay). Let's see what happens.

Devin, I'm wondering a bit about your statement and if you would read some comments here it seems that I'm not the only one being afflicted with this behaviour. However, there are several entries in HiFi's support forum and you would find me amongst them. By the way, when flying online with a couple of friends I can hear (and sometimes watch) others sharing this experience, too. As I have to leave now, I'm going to submit a ticket later today (I'm already registered)

Unfortunately all expectations that one of both interfacing companies would solve the overwhelming wake effect for the NGX failed. I have the latest Beta of ASN installed and forget to check the turbulence settings after the update (of course, they where set to default) and made a flight today with my brand new WX radar equipped NGX. The result had been a crash with likely no survivors (a A320 landed about 4 mins in front of me). What do we have now, a weather program requiring aircraft specific settings? A ridiculous idea I suppose. It seems to be something that should be resolved between HiFi and PMDG. At the moment the bird's behaviour is not controllable as long as the related effects are set within ASN to anything > 0. EDIT: If the fault is clearly on ASN's side I surely would expect a little bit of pressure on them from PMDG, probably together with Aerosoft (their Bus seems to have similar problems).

Actually you can get any relevant European chart here for free (http://www.ead.eurocontrol.int/publicuser/public/pu/login.jsp). You just have to register, that's it.

I agree! I've had to know this stuff while studying electrical engineering and I never had to recapitulate it again. Of course I forgot almost everything - non, je ne regrette rien.

Well explained Brian. I was about to pick up the water analogy again and then luckily decided to read the thread to it's preliminary (?) end. At the beginning I was asking myself if we would end up with Maxwell's equations. :huh:

That's a longer story. I've build my own database by using purely the existent airport and runway data of FSX. Unfortunately I didn't sort it by LAT/LON but by ICAO. This caused obviously the same problem as the NGX wasn't able to sort out all environment variables (according to PMDG's helpdesk). I think it had to do with run-time problems which is no contradiction. However, I shouldn't have mentioned it as this was definitely a very special case. EDIT: I forgot to mention, that the data format wasn't the reason!

I've had the same problem with the NGX quite a while ago. It had been fixed after re-installing it again. An other reason could be that the Navdata are corrupt for whatever reason. In such a case it might happen also with other PMDG birds (it's just guessing).

Mark, What happens if you use <ctrl>+<space> after loading the overhead panel view? This should reset any view to its defaults.