I had the same, but It was the Windows Security. Take a look there if sound.exe is blocked.Quote:
Originally Posted by Miatanet
Printable View
I had the same, but It was the Windows Security. Take a look there if sound.exe is blocked.Quote:
Originally Posted by Miatanet
same here with engine problems, taxi is ok, but when ready for take off, engines do not spooling up and my sound module is also no longer starting. I will check blocked files by windows and report.BrStefanQuote:
Originally Posted by Leonidas
It´s Always good to hear, to not to be alone with an issue :)Quote:
Originally Posted by Miatanet
Disabled all virus scanning and sound.exe is on again, but still no engine spooling. I gues I go back to previous version without weather radar. Stefan
I´ve checked again too, because it came into my mind that i haven´t broadcasted my new SSD where V5 is installed, but still have no engine Spooling up.So i turned back to previous Version too. Hopefully JL will take a look into it wat could be wrong.
You can try removing icing effect in my soft by adding the line in c:\A320FMGS\FMGS server\PERF\CFM\aircraft.cfg
AUTOICE=no
indeed, that did the trick. Engines spooling up normaly if this line is added. Thank you JLQuote:
Originally Posted by jeehell
Can someone please test updating the NAVDATA with the latest navigraph AIRAC 2006?
Looks like the FMGSserver.exe hangs and MORA.BIN is not being created. If I revert back to a former AIRAC (2001) everything works well (as always).
Just an issue on my system (P3Dv4.5)?
As FSX user I've just noticed both issues as well: FMGSServer.exe hangs after a while and complete wrong WPT position using Airways after SID!!
Example: EDDS/EDDK with SID TAGIK2H - Z3 - KETEK (which is the first WPT of FP after SID. This WPT is located about 300 nm westward of WPT TAGIK!!!!!!!!!!)
I immediately noticed that there were only 10 (and not 11) bin files generated (MORA.bin is missing)with Navtgraph AIRAC 2006. This might be the reason for this bug.
The last Navigraph DB 2006 build stops at 49%. Anyone with this? Regards
Yes,mee to !regards Pete
mee to, today LIML-EDDF give me about 1040 miles because some point was located in wrong position
Same at me. MORA.bin missing, Wayponts displaced, Database stops at 49%. Both P3Dv4 and P3Dv5, B53.1.0, AIRAC2006. EDIT: Went back to 53.0.1, problem disappeared with AIRAC2005, but appears again with AIRAC2006. Seems to be a Navigraph problem?
Same here but restarted computer and it works.MikeQuote:
Originally Posted by Leonidas
Haha, same to me, but database may be corrupted, isn't it?Quote:
Originally Posted by startrail
X-checked it: Yes, after reboot Database loads completely into MCDU, but waypoints are still displaced, so (Navigraph -?-) database seems to be corrupted. To be exact: Some, but not all waypoints are displaced, when I load a Coroute transferred by CorteManager4JH or when I put the route with airways into the MCDU manually. But when I clear the displaced waypoints and put only them, but not the airway manually into the flightplan in the MCDU, the waypoints appear correct. This appears as long as I have navrecord.dat with AIRAC2006 from Navigraph active, in this case MORA.bin is missing, when I let A320FMGS build new bins. The problem is gone when I have navrecord.dat with AIRAC2005 from Navigraph active. In this case the bins are built with MORA.bin.Quote:
Originally Posted by Leonidas
There seems to be some issues in the AIRACR 2006. I will report that to Navigraph.You can circumvent the issue by actually using AIRAC 2005 as DB1 and AIRAC 2006 as DB2 instead.
I put a full update on the updater which should fix the issue. NOt 100% tested so I hope it works, please report any issues such as procedures or waypoints missing etc...
Yes it is. The issue is from Navigraph. It is operational but waypoints are misplaced.Quote:
Originally Posted by Leonidas
Hi JH,Quote:
Originally Posted by jeehell
I would like to go on with version 52.5.6 and I don't mind to use DB of AIRAC 2005 for a while. Do you think that Navigraph will update/correct their current navrecord.dat or do we have to wait until AIRAC 2007? Or is it mandatory to install your full update to be able to use all future AIRAC from Naivigraph?
Regards
René
I use NavData Pro form Aerosoft and 10 bin files are created. Is that an issue, because i´ve heard there should be 11?? I´am not sure if in the past ever 11 bin files where created. I haven´t noticed any issues of wrong navdata with the actual airac so far.
I have no idea if they will correct that cycle. I sent them the details I could find. It is still Sunday, we'll see tomorrow...Quote:
Originally Posted by romeow
It seems normal. Aerosoft lacks a few things in the navdata such as MORA grid. This should be up to the same level as navigraph soon.Quote:
Originally Posted by bbruechmann
Thank you for your efforts! So we'll wait and see…..Quote:
Originally Posted by jeehell
THX a lot for the quick update - checked it with P3Dv5, now works perfect with Navigraph AIRAC 2006.
Hopefully not so soon. I´am also happy without some issues or lacks more…:)By the way, actually everything works fine with 53.1.0 including weather Radar with ASP3D in V5 and with EA. The issue with the "autoicing" that Prevent engines from Spooling up is the last i noticed beside the flightpath computation issue. The TOD is allways computed way too early. There must be something wrong in the descent profile.Quote:
Originally Posted by jeehell
Problem solved….. Simpatcher wasn't active…...
Problem solved….. Simpatcher wasn't active…...Quote:
Originally Posted by asessa
AIRAC 2006 Rev 2 is out! No problems anymore! Thank you JH!Quote:
Originally Posted by jeehell
Does it work with the last interim update or do we have to go back to B53.1.0?
It works with all versions.
Hi JL, i updated the suite, installed new version of airacas but bin file are not generated (after 15 mins).Any idea ?
Up... after reinstall airacs v2 it doesn't build the bin files... any idea? can i force bulding bin files?Quote:
Originally Posted by asessa
building the bin files normally only require deleting them before running fmgs server alone.
Which airac you use? Navigraph 2006 rev2?
Which version of the software?Here for me it is relatively quick (about 3 minutes)
Hi JL, yes i know the procedure : delete all bin files, install 2006v2 , start JL , after 15 mins no bin files was generate. I check logs but i didn't found any issue (i think).Quote:
Originally Posted by jeehell
Starting only FGMSServer.exe works! Thanks
With version B53.2.0 I have some strange behavior during ILS approach. 1st, I through it could be due to the Nav Database v2006, so I reloaded v2005 (see picture B53.2.0-01).
When I enter the approach configuration for LSZH ILS RWY 14, I receive the correct course 134 (see picture B53.2.0-02). But when I approach LSZH, the RADIO NAV shows a course of 130 (see picture B53.2.0-03). So I manually set the course to 135 (I took 135 to make sure I can differentiate between the 134 from the ARRIVAL set up). On the PFD (see picture B53.2.0-04a) to course is correctly shown as 135. However, the autopilot still navigates with course 130 as you can see in the same picture. As a result, the approach is way to much to the right with the LOC aligned to course 130 (see picture B53.2.0-04b). I disconnected the autopilot and manually aligned with the RWY 14 (see picture B53.2.0-05a and B53.2.0-05b). This shows that the course 134 shown during the ARRIVAL set up would be correct, but somehow it changes to course 130.
I have similar behavior for:
- LSZH ILS RWY 28
- EDDS ILS RWY 25
Note: both sceneries are from Aerosoft
I do NOT have this issue for:
- LSGG ILS RWY 22
Note: Scenery from FSDreamTeam
Another remark: I didn't have this issue prior to B53.2.0.
Thank you for having a look into this.
Adrian
this is strange. Did you apply Hervé Sors fixes? try to insert the following line in c:\A320FMGS\navdata\fsscenery.cfg:monitorARPT=LSZH then rebuild the navdata and post the c:\A320FMGS\logs\logndb.txt file just after rebuilding finishes
I tested the Hervé Sors and FSAerodata fixes. But I uninstalled both due to P3D crashes at LFSB. I also checked on the scenery screen within P3D v4.5 that those fixes are not listed anymore.Quote:
Originally Posted by jeehell
Please find attached the requested log file.
Thank you
Adrian
hmm I hardly see why Hervé's and FSAerodata fixes would crash P3D, they just change frequencies and runways QFU, hardly anything which could cause a crash.
However, your log is intriguing, because it says it cannot find any ILS in the BGL files for LSZH.
Also, it only found the stock BGL for LSZH, not an addon scenery file.
I would need to see your c:\A320FMGS\Navdata\fsscenery.cfg file as well to see what's in it.
And if you know, how your scenery is declared in P3D (via addon.cfg, via an addon.xml in your documents\P3D V4 files via direct entry in scenery.cfg?)