Jump to content

mburkhard

Members
  • Content Count

    179
  • Joined

  • Last visited

Community Reputation

76 Excellent

About mburkhard

  • Rank
    Senior Member
  • Birthday January 1

Contact Methods

  • Website URL
    http://www.flightsimlabs.com

Profile Information

  • Gender:
    Male
  • Location:
    Switzerland

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I had reported this half a year ago shortly after release, so the developer is aware that season textures do not match. Supposedly there's an update in progress for EGNX, but we haven't heard anything for months.
  2. Thanks for the info, it was not my intention to suggest you rush things. I'm disappointed to learn however that you won't fix the rest of the runway- and approach lights. As I had stated earlier, there are several issues with them. And I did offer to explain things and help you with it, so I'm not sure what else I can do to make you realise, that what you have done in the scenery is wrong. So I ask you to be open about this. In addition to fixing the alternating red/white centre line lights, will you: - add CAT3 approach and RWY lighting as it is there in reality for RWY32? - Move the REILs for RWY14 to the correct place at the end of the runway, and add the missing RWY edge lights accordingly? If you say no, that's fine with me, I can get it over with and ask for a refund. Because you do advertise "realistic approach and airport lighting", which for me includes CAT3 lighting if it is there on the real runway.
  3. @Greg Jones Can you give any time estimate for an update/fix to the EGNM product? And if yes, can you please confirm that approach & runway lighting will be aligned with reality? You having in the meantime released the next product already has me worried that fixing bugs is not a priority at Orbx
  4. If performance is important to you, you shouldn't buy EGPH at this time. Raz can of course say that 99% of his customers have "ultra smooth performance", but that doesn't mean anything. EGPH might be just fine when flying there using a small GA aircraft. However when I use complex airliners, I see FPS that are noticeably worse than they are at other airports of similar size. That's simply what I see. Orbx' own Gotheborg scenery for example, being similar in size to EGPH, runs so much better regarding FPS and smoothness on my system. One reason for this could be the over-use of PeopleFlow all around the airport. Dozens of them are placed everywhere, and the configurator does not allow you to reduce their numbers or disable them entirely. Maybe once that issue is addressed, perhaps things will improve. We'll see. But for now, when it comes to performance, I can't recommend EGPH.
  5. Good to know, thanks! You might want to update the screenshots on the product page then
  6. @Greg Jones While you look into providing a possible update, could you perhaps tweak the tower night lighting to something a bit more realistic? It is highly unrealistic to see an ATC tower being brightly lit up on the inside, as this would make it impossible to do ATC at nighttime. Think about it, sitting in there, how could you possibly see anything when looking outside So to make it look realistic you should drastically reduce the lighting visible on the tower windows for the night textures. Or, if that is too complicated, remove the lighting entirely. No light inside the tower is more realistic than flood lights. Thanks, Markus
  7. I reported this to Andreas a few months ago. He confirmed the issue and promised to resolve this in an upcoming update.
  8. Looking good so far! One thing though for night lighting: Please don't model tower windows like this, with lights as bright as a thousand suns. Simply ask yourselves this question: How would the tower controllers be able to see ANYthing when trying to look out of these windows when it's dark outside? Exactly, they wouldn't see a thing. Real tower windows show only very small amounts of light inside the room. And if that is too much of a hassle for you to do, simply remove the tower windows night lighting completely. It would be much more realistic than what you have now.
  9. There is no winter (snow) texture included with EGNX. So it doesn't fit into the surroundings during hard winter season. Other seasons are present, but if I remember correctly the switch from Winter to Spring is misaligned by a month or so.
  10. Once the patch is out, Leeds will be perfectly fine. No magic required, correct runway- and approach lights, sort out the static car park vehicles, and include an optional SODE VDGS. That's all really, so perfection is not far off. As for EGNX, this is a different developer who still needs to show that they are capable of doing quality work. Many months after release and there's still no update in sight. Proceed with caution on that one.
  11. Just want to confirm this, in case others have the same issue. Disabling parked cars cures the major stutters I had.
  12. Both. At the hint of another user in another topic I have disabled parked cars, now stutters are completely gone. So those cars seem to have a pretty disastrous effect on my system. Something with their modelling or texturing technique causes major stutters. Just to reiterate, I'm not talking about a "bit of stuttering during movement" due to texture loading. But rather major rhythmic stutters that come and go during movement, even when moving past the airport and it is already located behind my POV. In other words, unusable. This does not happen at any other ORBX scenery I have, and I usually don't need to deactivate parked cars. And as I had said, it is certainly not an issue of low FPS. That's why I suspect that something specific to your cars is causing this. In any case, I can live with having parked cars disabled. But if me and another user has this issue, it does not seem to be specific to my machine. Sorry to bother you again with this. There is another inaccuracy with your REILs. They need to be placed across the runway, not past the edge of it. In fact the red lights do NOT feature wing bars, only the green ones do (as you have modelled correctly). Because you had incorrectly placed the red lights at the same location as the green ones, you assumed that you'd also need to model wing bars for the red lights. This is not so, the red lights only mark the physical width of the runway, they do not extend beyond the runway edge lights. This is taken out of the AIP. You may message me if you need further explanations on the runway lighting topic. It is all evident from the AIP, plus these things tend to be heavily standardised according to ICAO standards, which means guessing is not needed usually, one can simply apply ICAO standard. You mentioned above that you model those things according to the photos at hand, which I guess is not always sufficient when it comes to things related to runways, unless you fly to the airport yourself at night If you combine AIP information as well as knowledge of ICAO standards with your imagery, this could lead to more accurate results without the pain of guessing. But as I've said, message me if you need more info, I work for an air navigation service provider, airport facilities and ICAO are part of my day job. So I'm happy to explain things!
  13. Indeed. As I've said, the red colour is fine on one end, but not on the other. I apologise for not making myself clear enough. What I was trying to say is that what you have modelled right now is impossible in reality. You have the centreline lights running PAST the REILs. This cannot happen in reality. Think about it, why would you continue parts of the runway lighting after marking the end of said runway? It's either a runway, or a taxiway, but there can't be partial runway lighting as you have it now. Anyway, the AIP has confirmed my suspicion. I'm a bit surprised that ORBX does not seem to check the UK AIP. See the attached PDF: You need to move the red REILs to the physical end of the runway, they do NOT coincide with the location of the green threshold lights. This also means that you need to extend the runway edge lights to reach until the physical end of the runway as well. (as a side note, please be aware that not all things on this AIP chart are to scale, they mostly have a schematic purpose only) And just to make sure, you will add the CAT3 specific lighting for RWY32 as well, meaning different approach lights as well as TDZ lights? Just asking because you have ignored my mentioning of that omission so far. 73112.pdf
  14. Thanks for your response Greg. Your quote from the CAA handbook is perfectly fine, however that is not what I see for RWY14. In my sim (P3Dv4) I see the centreline lights correctly alternating between red and white, however, instead of ending in red, they are completely white until the end of the runway. It seems to be fine for RWY32 though. Having said that, what is not correct is the runway edge lighting for both runway ends. It does not make sense to have centreline lighting, but no edge lighting on any part of a runway. However that is the case on both runway ends right now. What is also wrong is for centreline lights continuing AFTER the red REILs, which also is the case on both ends of the runway right now. As I have said, I suspect that the REILs are placed at the wrong spot on both ends. Great to hear that you're considering adding optional SODE VDGS. They are of great quality and will enhance the scenery quite nicely. I hope you'll also add CAT2/3 lighting for RWY32? One more thing: I experience major stutters on this airport. Frames are perfectly fine (50-60 in my test case). But when moving across the airport I observe major stutters, almost in a regular interval. I do not have this issue on any other airport installed, ORBX or otherwise. It is unique to EGNM. Has there been anything like that reported by your testers or other customers? Thanks, Markus
  15. Dear ORBX. I've just installed the new ENGM scenery, and I like what I see! A good step up from the previous two UK releases Midlands and Edinburgh. Also a big thank you for providing multiple seasons config options so that it matches perfectly with the surrounding scenery in all cases. Here's a couple of issues I have found so far: I'm afraid the approach- and runway lighting is quite a mess. The runway lighting at the END of both runways is inconsistent with reality. It doesn't make sense for the centreline lights to continue past the REIL or that as in case of runway 14, the centreline lights switch from alternating between red and white to pure white towards the end. That is incorrect. Please also check the position of the REILs. I'm not sure if they indeed correspond to the position of the opposite runway's displaced threshold IRL, I very much doubt it. Also missing is the CAT2/3 approach- and runway lighting for runway 32. You modelled the same type of lighting as on the opposite runway, which is CAT1 only. RWY32 needs CAT2/3 approach lighting AND standard TDZ lights, which are also missing. You do advertise "realistic approach lighting" after all I see that the APIS parking system for stands 7 and 8 is missing. Would it be possible to create an optional config file for the SODE VDGS pack? That way people using that pack could activate proper VDGS for those stands in ORBX Central? I see there are no animated service vehicles. This is a bit confusing. As evidenced by other ORBX airports, you do have the technology. Why not include some on this airport, since it does feature service roads? Doesn't need to be a whole armada, just a few vehicles so that the airport doesn't look as lifeless as it does currently. That's all for the time being, thanks for listening!
×
×
  • Create New...