|
|
Post by paulnd on May 2, 2019 15:08:47 GMT
Hello, I don't know if you have been contacted about a possible elevation issue with Flightbeam SEQM? It appears that \0304\scenery\APX27320.bgl causes cliffs surrounding the runway and taxiway. Restoring the default P3D v4 APX27320.bgl resolves the issue. There's a discussion and screenshots on the Flightbeam forum flightbeam.net/forums/viewtopic.php?f=40&t=3324Could you possibly look into this please? regards Paul |
|
|
|
Post by Herve Sors on May 2, 2019 17:45:34 GMT
I will although I'm not sure I can access their forum and I only can test FSX
Not at home at this time. Will do that on next Sunday or Monday
Hervé
|
|
|
|
Post by paulnd on May 2, 2019 18:12:30 GMT
Thank you.
Unfortunately Flightbeam only develop sceneries for P3D now but perhaps the devs could work with you to resolve the issue so that we can continue to use your updates with their scenery
|
|
|
|
Post by Herve Sors on May 2, 2019 19:01:51 GMT
Paul
Considering the changes I performed only concern navaids, some runways, approach lights, PAPIs & airport names (without any change to any altitudes or scenery objects and without any decompilation/recompilation of BGL files), I'm a bit puzzled by the problem that was described. However, one possible cause could be that the P3D file is not similar to the FSX file I use for performing and providing the changes. This would be very unusual since P3D did not change the content of all files I analyzed as compared to FSX but this hypothesis cannot be excluded. Could you send me by private email, the original P3Dv4 APX27320.bgl file so as I could have a look. Considering users WITHOUT the Flightbeam scenery did not report any problem, it could also be due to some exclude problems in the Flightbeam scenery not working as expected with the modified APX BGL file. In such a case, it will be hard to solve on Flightbeam's side considering they base their design on the unmodified stock sim files
Thanks by advance
Hervé
|
|
|
|
Post by Herve Sors on May 5, 2019 16:57:55 GMT
I carefully analyzed changes I performed to the stock APX27320.bgl file that may impact rendering while addon scenery was installed
(Note there is no problem in the sim if no addon scenery is present)
The only significant things were:
- Change of ICAO indicator from SEQU to SEQM
- Rwy renumbering from 17/35 to 18/36 (with adequate change of taxiway signs)
- Correction and addition of current ILS data (IQN and IQS instead of IQO)
- Correction/addition of approach lights and PAPI data
- Update of COM data
There was no change in altitude data and scenery objects (except ILS associated objects)
I think the first 2 may affect some exclusion parameters in the scenery addon (to be discussed with addon developpers)
This is the only cause I can identify by now
Tha updated file display is OK when there is no additional scenery
The P3Dv4 BGL file is strictly identical to the FSX one
Hope it could help sorting out the problem
|
|
|
|
Post by niksan29 on Aug 15, 2019 7:56:35 GMT
Does your installer create this backup .bgl.ilsbckup?  If the file APX27320.bgl.ilsbckup is renamed to APX27320.bgl then everything is fine with elevation  |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 27, 2019 0:57:18 GMT
I can confirm the issue in P3D .... no matter what add on i use for SEQM (downloaded a free one for FSX and converted it to P3D4) and had the elevation issue at SEQM , i think you said a while back Herve that your updates are based on FSX files even for P3D, it looks like this can cause issues with P3D default Airports and add on airports for them sadly .. renaming the file back to the default fixed it.
Thanks
Rich
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 27, 2019 1:11:42 GMT
I carefully analyzed changes I performed to the stock APX27320.bgl file that may impact rendering while addon scenery was installed (Note there is no problem in the sim if no addon scenery is present) The only significant things were: - Change of ICAO indicator from SEQU to SEQM - Rwy renumbering from 17/35 to 18/36 (with adequate change of taxiway signs) - Correction and addition of current ILS data (IQN and IQS instead of IQO) - Correction/addition of approach lights and PAPI data - Update of COM data There was no change in altitude data and scenery objects (except ILS associated objects) I think the first 2 may affect some exclusion parameters in the scenery addon (to be discussed with addon developpers) This is the only cause I can identify by now Tha updated file display is OK when there is no additional scenery The P3Dv4 BGL file is strictly identical to the FSX one Hope it could help sorting out the problem Im wondering .. you changed the ICAO from SEQU to SEQM .... but SEQM is a new airport build a few miles away from the old SEQU .. so in effect you have put the new airport in the same spot that SEQU was ... hence maybe causing the terrain issues issues...could that be it ? Thanks
Rich
|
|
|
|
Post by Herve Sors on Aug 27, 2019 6:34:21 GMT
Hi Rich
You're right and I must say I didn't check for that. Consequently, and as far as SEQU is now closed, I will revert changes I made and disable all SEQU facilities (effective on next update)
Of course SEQM will not exist as far as it is not part of default FSX/P3D scenery
Thanks for the information
Hervé
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 27, 2019 14:40:20 GMT
Too the other two users ...If you have updated the navdata then for a quick fix untilll the new data set is out use the Airport inspector and editor program from Herves site, open the updated APX27320.bgl file and rename SEQM back to SEQU and see if that helps.
Rich
|
|
|
|
Post by Herve Sors on Aug 27, 2019 16:25:55 GMT
Guys A (temporary) updated file is available here www.aero.sors.fr/beta/APX27320.bglReplace the old one in the Scenery/0304/scenery folder (ensure you already have a corresponding original .ilsbckup file) |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 28, 2019 15:08:37 GMT
Thanks Herve great suppport as always
Rich
|
|
