Jump to content

mischung

Members
  • Posts

    18
  • Joined

  • Last visited

mischung's Achievements

  1. Hi Urs, thanks for coming back to this issue. Hopefully this could be solved, but since this was the first time I had such a problem it's not a big deal πŸ˜‰ Maybe I should switch to NavDataPro (LIDO Data) next time πŸ˜‡ Have a nice weekend! Marc
  2. Thanks Oskar for your investigation and sorry I'm coming back to this so late πŸ˜• I just did an update of my nav-database to the latest cycle 2104 and unfortunately the problem persists. The only entry in the log files is also the same as before: 2021-05-01 13:16:14.096 Error : UngΓΌltiger Parameter. bei System.Drawing.Drawing2D.GraphicsPath.AddArc(Single x, Single y, Single width, Single height, Single startAngle, Single sweepAngle) bei System.Drawing.Drawing2D.GraphicsPath.AddArc(RectangleF rect, Single startAngle, Single sweepAngle) bei i.i.r.n.r2.j(ix A_0) bei i.i.r.n.r2.i(i8 A_0) bei i.i.r.n.r2.i33(Graphics A_0, n A_1) bei i.i.r.o.j.k.i(Object A_0, PaintEventArgs A_1) ... (repeated) What is interesting is, that the affected STARs are on the same approach chart(s), so something has to be wrong/different with this Navigraph data 🧐 Jeppesen 10-2: DARM1R, DLAL1R, IGRS1R Jeppesen 10-2A: KMTI1R, MUNA1R The other two charts/approaches are working: Jeppesen 10-2B: BIDUR, NAYAK Jeppesen 10-2C: ROME2R, ROMEO, SMR, SMRA2R Would be great if you could check the Navigraph data in this case. I could also open a topic in their forum if you think that makes sense. Cheers
  3. Hi! On today's flght I encountered a problem where the route drawing completely disappears, when selecting a STAR to VNKT. This happes for the follwing STARs: DARM1R, DLAL1R, IGRS1R, KMTI1R, MUNA1R. The other arrival routes seem to work just fine. My setup: P3D V5.1.12 Navigraph Cycle 2103 P3D-World and Airport Navaid Update from Herve Sors (but disabling and perform da DB-rebuild made no difference πŸ˜‘) The Log also is showing some errors, which might help to identify the problem (attached also the support file for the client): 2021-04-05 13:16:21.255 Debug : Active airport changed to VNKT (M) 2021-04-05 13:16:21.308 Warning : Could not determine whether MAP is before or after THR. (VNKT, R02, RATAN) 2021-04-05 13:16:21.583 Error : UngοΏ½ltiger Parameter. bei System.Drawing.Drawing2D.GraphicsPath.AddArc(Single x, Single y, Single width, Single height, Single startAngle, Single sweepAngle) bei System.Drawing.Drawing2D.GraphicsPath.AddArc(RectangleF rect, Single startAngle, Single sweepAngle) bei q.q.t.j.tp.z(q5 A_0) bei q.q.t.j.tp.q(qc A_0) bei q.q.t.j.tp.qzz(Graphics A_0, j A_1) bei q.q.t.s.z.i.q(Object A_0, PaintEventArgs A_1) 2021-04-05 13:16:21.746 Error : UngοΏ½ltiger Parameter. bei System.Drawing.Drawing2D.GraphicsPath.AddArc(Single x, Single y, Single width, Single height, Single startAngle, Single sweepAngle) bei System.Drawing.Drawing2D.GraphicsPath.AddArc(RectangleF rect, Single startAngle, Single sweepAngle) bei q.q.t.j.tp.z(q5 A_0) bei q.q.t.j.tp.q(qc A_0) bei q.q.t.j.tp.qzz(Graphics A_0, j A_1) bei q.q.t.s.z.i.q(Object A_0, PaintEventArgs A_1) ... (repeated) 2021-04-05 13:16:21.785 Warning : Could not determine whether MAP is before or after THR. (VNKT, R02, RATAN) 2021-04-05 13:16:22.575 Warning : Could not determine whether MAP is before or after THR. (VNKT, R02, RATAN) ... (repeated) 2021-04-05 13:16:22.838 Error : UngοΏ½ltiger Parameter. bei System.Drawing.Drawing2D.GraphicsPath.AddArc(Single x, Single y, Single width, Single height, Single startAngle, Single sweepAngle) bei System.Drawing.Drawing2D.GraphicsPath.AddArc(RectangleF rect, Single startAngle, Single sweepAngle) bei q.q.t.j.tp.z(q5 A_0) bei q.q.t.j.tp.q(qc A_0) bei q.q.t.j.tp.qzz(Graphics A_0, j A_1) bei q.q.t.s.z.i.q(Object A_0, PaintEventArgs A_1) If you need any further information just let me know πŸ™‚ Marc Client_202104051407.txt.zip
  4. Hi Oskar, hi Ray, just saw this thread and wanted to let you know, that LM did update the airport database in P3D V5 for the first time. There was no update to the original FSX-database from P3D V1 to V4. Unfortunately the P3D V5 database is already outdated again, because the database used is from the year 2017 (don't know the exact cycle). I guess that was the time when developement started and because they did not do a lot of changes to the BGL-format (despite the sloped runways), there is still no "easy" way to update these data more frequently (thinking of a database or similar). Also HervΓ© Sors will not provide updated BGL-files for V5 due to copyright reasons πŸ™ So one has to use his AIE-tool (airport inspector) to find discrepancies and perform the updates manually. But for your information, Dhaka has been updated in Stock P3D V5 πŸ˜‰ From: VGZR - Zia Intl - Dhaka To: VGHS - Hazrat Shahjalal Intl - Dhaka I contributed to a topic in the ORBX-forum regarding changed ICAO-codes from V4 to V5 (included some csv-lists there), so if your are interested you can find it here: Link Cheers! Marc
  5. Hi together, the navdata-update is a real dilemma of course 😜 Herve Sors updates are really good, but only update stock airports. This is not working out with standard addons like Vector (which adds a lot of elevation corrected airports! - with old navdata of course) fsAerodata follows a different approach, it deletes the airport navaids that are outdated and adds an updated version to the top scenery priority (with a provided fix it also works regarding the elevation issues after 4.5HF2). Still the problems with addons remain, because these navaids will not be disabled, so it may happen that there are several ILS-facilities for a specific airport. Also the addition of these ILS-facilities in a separate scenery layer is done a bit unconventionally and therefore EFB is not compatible with it πŸ™ The perfect tool would do it this way πŸ˜‰: Scan the scenery library and identify all available airports (only those with the highest priority of course / also considering addons) Identify the airports which need an update of their facilities (ILS, NDB, RWY ID, etc.) Change that specific airport and update it, changing the navdata inside the BGL itself. But I would guess one would run into some copyright-problems doing that approach and that's the main problem with it... Marc
  6. Hi Oskar, here is a post from Rob McCarthy confirming the upcoming hotfix: AFAIK there are several issues that should be addressed with this fix: - flying into invisible mountains on approach - some issues with the updated airports/landclass - lot of CTD-issues - VRAM-issues So this time it seems there are some major issues putting pressure on LM to bring out this hotfix quite fast. For me P3D V5 is performing quite nice at the moment, but I did not operate too many flights right now πŸ™‚
  7. Sorry Oskar, of course you do not need the P3D Hotfix for EFB2 to work. Just wanted to say, that the Hotfix is around the corner and in my opinion it would be a good idea to wait for that as well for a good start... I definitely chose the wrong words in my previous post... πŸ™ˆ Marc
  8. You will have to wait for the V5 hotfix from LM anyway πŸ˜‰πŸ˜‚ At least I will do that πŸ˜„
  9. Hi lunix, there are two other threads about compatibility already. Link to one of them.
  10. That it's working is not too unlikely, but creating a new database will not be possible. So please don't do it right now! See the following answer from Oskar: Link At the moment use it for display only πŸ˜‰
  11. There's a topic on this already: Link Urs first has to check on the new/changed Bgl-Files in V5, but I'm sure he can dort it out πŸ™‚ As far as I can see we then should have up to date navdata in P3D for the first time without the need of any 3rd party addon! Marc
  12. Hey Urs, thanks for your reply. Thought that maybe you had the chance to be on the beta of P3D V5 πŸ˜‰ There will be some changes in the airport data regarding the sloped runway feature I guess, as Pete Dowson already mentioned that over at the Prosim-Forum (he adapted his tool "MakeRunways" accordingly). I'm not really sure about the line "Updated over 24,000 airports with new data across the entire globe." in the changelog πŸ€” Of course it would be great to have a complete update off all navigation data, without fiddling around (ok Orbx Vector airports will still be a problem πŸ˜‚). Think we'll have to wait and see, but despite all the negative comments around the forums, I'm quite excited to see the next update of P3D and I think it offers great opportunities. Wish you Happy Easter and stay safe during this crazy time πŸ™‚
  13. Hi Aivlasoft-Team, I know P3D V5 is not yet available, but maybe you can shed some light, if EFB2 will be compatible with the new version or maybe needs an update? πŸ˜€ Take care. Marc
  14. Hi Jeff, you should try EFB Build #109, which is available from today. Urs fixed some problems regarding FSAerodata and also improved the matching of ILS-facilities to runways. For me this new build works perfectly, so hopefully your problems can be fixed too πŸ™‚ Regards Marc
  15. With Build 109 of EFB, which is available today, the above mentioned problems are solved! πŸ‘ Urs managed to change the data-extraction from FSAerodata files and also fixed some problems with matching runways to the correct ILS-facilities. On my side (with FSAerodata and ORBX OpenLC) all approaches on several airports I have tested are now visible, so just give it a try πŸ˜‰ Marc Note: Circling approaches (e.g. some approaches in LPMA) cannot be displayed at the moment, because this data is not included in the Navigraph or Aerosoft Datasets.
×
×
  • Create New...