NavDataPro
All support regarding NavDataPro
389 topics in this forum
-
Pinned topics
-
- 3 replies
- 9422 views
-
- 49 replies
- 16938 views
-
- 1 reply
- 5059 views
-
Topics
-
- 3 replies
- 71 views
-
- 26 replies
- 1724 views
-
- 1 reply
- 99 views
-
- 3 replies
- 91 views
-
- 3 replies
- 112 views
-
- 2 replies
- 108 views
-
- 1 reply
- 93 views
-
- 4 replies
- 165 views
-
- 1 reply
- 211 views
-
- 2 replies
- 247 views
-
- 5 replies
- 519 views
-
- 5 replies
- 602 views
-
- 5 replies
- 430 views
-
- 5 replies
- 570 views
-
- 5 replies
- 564 views
-
- 3 replies
- 525 views
-
- 6 replies
- 506 views
-
- 6 replies
- 649 views
-
- 16 replies
- 3699 views
-
- 7 replies
- 621 views
-
- 6 replies
- 648 views
-
- 1 reply
- 614 views
-
Posts
-
By Jose Zubillaga · Posted
Hello Dave, check the navdata airac that comes by default with the airbus and the error came back in the log, look for the points and there are also as in navigraph, I invite you to look at that error well, maybe that affects the calculations and Maybe the problems originate, especially when descending Thank you -
I wish I would have looked at this earlier. I've spent many many hours because of stutters and CTDs. I updated to 4.4 and it seemed ok but didn't realize it until now that this is probably the issue I ran into. I bought the Airbus product just after Xmas and a little after I loaded 4.4. Flights got so bad with hesitations and then CTDs I finally got rid of 4.4 and went back to an image with 4.3 on it. Then loaded 4.3 and had the same issue after loading the Airbus again but still didn't realize it. I reloaded an earlier 4.3 image and everything has been fine, however, I haven't loaded the Airbus yet. I was about ready to but thought I might check this forum. Glad I did. I'll wait until you have it fixed before I do. Please let us know when it is resolved. Thank you DagelijksGamer for finding this. Thank you Mathijs Kok for making sure this gets resolved. System
ASUS ROG Maximus X Hero (Wi-Fi AC) 300 Series Intel Z370 HDMI SATA 6Gb/s USB 3.1 ATX Intel Motherboard
Intel Core i7-8700 Coffee Lake 6-Core 3.2 GHz (4.6 GHz Turbo) LGA 1151 (300 Series) Desktop Processor
EVGA GeForce GTX 1080 Ti SC2 11GB GDDR5X Graphics card
G.SKILL Ripjaws V Series 32GB DDR4 SDRAM DDR4 3200
Intel SSD 600p Series (1.0TB, M.2 2280 80mm NVMe PCIe
WD Black 1TB Performance HD
WD Blue 4TB Hard Drive
Windows 10 Pro 32-bit/64-bit
Cooler Master Storm Scout 2 Gaming Mid Tower Computer Case
Alienware - AW2518H 25" LED FHD GSync Monitor
MasterLiquid 120 All-in-one CPU Liquid Cooler
EVGA SuperNOVA 750 80+ GOLD, 750W PS
LITE-ON DVD Burner Black SATA
ASUS Black Blu-ray Drive SATA
-
By Walter Almaraz · Posted
Hola Josemari, Disculpa en la demora de mis pruebas, te comento que no encuentro problemas con el Fuel Planner ya sea para FSX/P3Dv3 y P3Dv4 ambos pueden coexistir sin ningún inconveniente, para evitar inconvenientes tal vez quieras crear accesos directos en el escritorio para evitar confusiones. Saludos, Walter -
By Sabretooth78 · Posted
I've reinstalled several times in the past several weeks and at least one of those times I tried deleting those "User" folders (and then restarting) but to no avail in stopping the problem, so apparently it's one of those "your mileage may vary" things that happened to work for you... I also don't run A/V - I don't use my sim PC for anything besides simming (and the attendant downloading that goes with it) so unless SimMarket, ORBX, Aerosoft, etc. get hacked; well, suffice it to say I haven't used A/V on any of my PCs (Mac and Windows) in at least 15 years and haven't got burned; I'm tech savvy enough and back up early and often enough that if I did get a virus I'd just assume wipe clean and restart. But I digress... One area where I differ from your process is that I tend to run P3D and load up whatever particular add-on (particularly in the case of aircraft) immediately after running the installer and rebooting. I'm not sure if that makes a difference. I guess I do it as sort of a holdover from the FSX days, where you had to run FSX on the clean install in order for the sim to create its cfg files and such before installing the service packs, otherwise you could potentially run into problems. All that said, I now almost ALWAYS get the managed speed bug on climb when hitting crossover altitude. Always, as in, at least the last 7-8 flights (beginning around New Year's Day). Before that, it hadn't been happening at all (in that situation). Fortunately, George still seems to obey the "proper" climb speed, and the bug is easily eliminated by either pushing or pulling the altitude knob. As for the random occurrence of the bug during flight, I still get that only sporadically. Say maybe once every 5 flights. For instance it happened to me last night fairly early in cruise on a 4:45 flight; it seems to have a propensity to occur on longer flights (which makes sense; longer flight = greater chance of it happening eventually) at some random point in between waypoints. The first time it ever happened to me was on November 5; about midway through a 5 hour flight. Naturally, that was while running P3D v4.3, and the problem has persisted through the P3D update to v4.4 (for which I updated all components and have since reinstalled the Bus a number of times). Also consider I just performed a clean install of Windows in mid-August 2018 when I effectively rebuilt the PC. I don't know if that rules out the state of my P3D install as a cause or not. My virtual money is on it being an unintended side effect caused by a VNAV update to the Bus sometime in late October/early November, but that's just a hunch and I don't intend that as a dig at the developers; --it happens. So, regarding the upcoming update. The change log for 1.2.2.2 said that the logging would be triggered when the managed speed dropped below 120 kts. Unfortunately, this would not trigger in the vast majority of my situations where it is occurring during climb, where it typically shows up at about FL260, calling for a speed of 180 kts and slowly decaying as the climb progresses. Could I make the suggestion that the logging instead be triggered say when the managed speed drops below 200 while in climb or cruise phase? Or perhaps any situation above say FL200? Naturally it would have to be coded in some way so as best to avoid instances in initial climb with lower speeds such as SIDs with speed restrictions, etc. Of course I may well be the only one having this issue during the climb. At this point I'm sick to death of reinstalling things and I'm content just to throw it into selected speed until the issue is teased out and squashed, which will happen eventually. I have no problem doing some investigative work as part of my normal flying, but I'm done with the reinstalling for now. There's enough to do as it is just in the normal course of updating, regardless of trying to tease out bugs. I have no regrets jumping ship to P3D, but this is why I clung to FSX for as long as I did, why I would still be using FSX were P3D still only 32-bit, and why with most gaming I've usually been a hold out; I appreciate the maturity and stability in the platform! -
It's very good. Much appreciated. Thank you. Bruce R
-