Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

106 Excellent

About TymK

  • Rank
    Life Member
  • Birthday 01/24/1975

Profile Information

  • Gender:
  • Location:
    Torun, Poland
  • Interests:
    Freelance translator
    Aviation/flight simulation, military history

Recent Profile Visitors

1,034 profile views
  1. I was referring to the difference in how textures are displayed in V4 and V5 as shown in the screenshots earlier in this thread, see this post.
  2. This is the latest feature offered by LM's "early-alpha-advertised-as-beta" implementation of the Enhanced Atmospherics / TrueSky option... ;-) /sarcasm off Unfortunately, that's a new bug introduced by HF2, this happens in a lot of places and only affects some objects... Essentially, the objects show through the volumetric fog, so the closer you get to them, the more they "blend in" with the surrounding scenery as the fog/haze gets thinner. It has been reported in the LM forums, but so far, there's been no response from the team.
  3. Does that include the texture transparency issue? No change in that respect at my end, unfortunately...
  4. Are you absolutely sure you're getting outdated frequencies with P3D version 5? I've seen a lot of updates to the default navdata, so (at least theoretically) third-party nav data should not be needed... Can you post details of some of the airports that remain incorrect in v5?
  5. The GPU may be a bottleneck in some scenarios, but I recently tried XP11 and TE GB South on my new "work/light gaming" laptop with a mobile 1650 and was very pleasantly surprised with how well it ran. Certainly above expectations. If you can live with lower antialiasing settings, absolutely give it a try. The GB demo gives a nice overview of performance, especially in the denser urban areas.
  6. I've also noticed it at 11S, 0S9, KORS, 1S2 and 3W5. Things seem fine at S43, though. Perhaps different techniques were used to overlay the runways/taxiways at different airports, so it'd be great if Jarrad could chime in on that from a technical perspective. Here's an example from 1S2. It doesn't look too bad in terms of resolution, but you can clearly see the shape of an airplane from the underlying photoreal background showing through the apron texture:
  7. It's a (more or less) known issue with P3D v5, reported in other threads. Essentially, v5 makes runway/taxiway polygons more transparent that v4 and earlier versions, so the underlying lower-res ground polygon shows through the higher-res runway/taxiway textures. When you look at the taxiway lines/markings, you can see that they are there, but hardly visible due to the transparency issue. Let's see if the highly-anticipated hotfix 2 for v5 helps. If it does not, then I suppose we'll need to ask Orbx devs to revisit the issue...
  8. The file isn't present in my v4 installation, either. Are you sure it's needed? Has it been reported as missing in an error log? The base file (Aurora_lib_buildings_industrial_01.dds) only contains some structural parts which may simply not require a light map (the files with an LM suffix are light maps that add lit windows, etc. to the base texture at night).
  9. Looking good now! The "Sync" option is actually very clever and has helped me resolve many of my silly user scre... I mean user errors... As for the layering, that's a weird one, but the manual move works, so all is fine here as well. BTW, big thanks to Nick for his patience (and a little apology for my impatience before...). The transition to P3D v5 has generally proven to be a bit less smooth that we'd all expected, so a lot of small niggles are bound to surface. Regards, Tym
  10. This is actually a weird issue that started happening for me when the move to the "add-on.xml method" was made. Are your add-ons installed in a library or in the sim directory? When using a library, the only way to make the sheds/caravans disappear is to move WA56 manually above all other Orbx entries in the scenery library. It applies to both v4 and v5. BTW, I've just noticed the same issue in Dario's post in the screenshot thread, see the first one...
  11. I thought I'd just give it a gentle bump ;-) Any news on the ground poly issue?
  12. Hi Nick, Thanks for taking the time to get these shots, now I see why you focused on detail1.bmp in this case. It appears there may have been some transparency / bleed-through in both FSX and past P3D versions, just not as pronounced as in v5, which is why it went largely unnoticed. This may well be the case with 11S, too, but let's wait and see what Misha comes up with, perhaps it's an easy fix... Cheers, Tym
  13. Nope, not any longer, but I flew extensively from 11S and the issue was not there. As for Welshpool, here's an example of a flight in FSX which shows that none of the bleed-through seen in P3D v5 occurred in that version:
  14. I'm afraid we're running in circles here, but... no, it should not. The problem is that with correct layering/blending, the runway polygon should completely obscure the underlying ortho AND the detail1.bmp that is applied to it. P3D v5 has changed that (as confirmed by Larry R.), which is the reason why the ortho and detail1.bmp show through. Once again, this should not happen and in fact (as shown by various pre-v5 shots) did not happen in FSX and in P3D up to and including v4.5. EDIT: Some old AU airports and the freeware KHQM did not use separate polygons (I think KHQM has a runway poly, but taxiways use only the main ortho and detail1.bmp shows there, but, once again, this was only the case with some of the earliest products).
  15. I don't think it has, though... Larry has clearly confirmed that the manner in which ground polygons are blended into terrain has changed in v5, so let's see what Misha says.
  • Create New...