Jump to content

John Burgess

Orbx Team
  • Posts

    3,335
  • Joined

  • Last visited

  • Days Won

    16

Everything posted by John Burgess

  1. Hi Rob and Chris, Cityscape should have a higher priority than the Fly Tampa scenery to ensure that the Cityscape PR is being used outside the airport perimeter. I saw exactly what you describe in testing when having the airport at a higher priority (with both sceneries installed via OC this happens automatically). From what I remember the missing autogen is in the areas outside the FT scenery PR area so the FT scenery doesn't include autogen for those places. The ghost docks are where the Cityscape PR is showing a more extensive dock area than FT (presumably the docks have been extended at some point). Hence the need for Cityscape to have the higher priority. Using the CP option for compatibility with the FT scenery should, hopefully, remove the buildings from the Cityscape scenery which would duplicate those in the FT scenery. All the best, John
  2. Hi Ian, Difficult to know exactly what to suggest but here's my experience. There is a CP option to use 2k textures for the city - using that and setting the texture resolution to medium in the sim (1024) I'm getting about 5GB out of 7.1 with the cityscape, AUv2 and Fly Tampa under circumstances where I'm getting about 4GB usage without the Cityscape (fair weather with the Bell Jetranger helicopter). Setting texture resolution to High (2048) in the sim I'm getting about 5.5GB with the cityscape (but at times creeping towards 6). I have an 8GB card and am using P3D v5.3. All the best, John
  3. Keeping my fingers crossed - it works fine for me at the moment and I'm hoping it'll keep the grandchildren quiet for at least 5 mins when they visit! Santa suffering a CTD might traumatise them for life Hope the problem can be resolved. All the best, John
  4. Hi there, Edit - forgot to say you should try the advice in this post first. You could also try verify files or just uninstall\re-install. I've got the scenery installed in my community folder and don't see any obvious problems. If the issues persist support is provided by the developers, MK-Studios. http://mkstudios.pl/support/index.php All the best, John
  5. Hi Kevin, Spent too much of my life trying to make sceneries play nicely together! I doubt there is a simple solution to this one and I suspect it's technical. From what I recall the most obvious consequence of de-activating the file is a loss of autogen vegetation in some places. All the best, John
  6. The one time I remember having discussions about this type of file was with Sascha Normann when it's absence was causing a loss of certain autogen objects in some of our sceneries. From what I remember it was to do with making sure our sceneries were looking for their autogen in the correct 'Region' within the autogen configuration files. Never did fully understand the details! Why it causes the loss of ES autogen I don't know I'm afraid (I see the same in P3Dv4) but it's removal will cause some missing patches of autogen in the TEGB North area. All the best, John
  7. Just to check I installed the Fly Tampa scenery in v5 and, unfortunately, what worked for me in v4.5 doesn't work in v5. Like you I've not found a way of disabling the FT photoscenery without autogen appearing over the airport. The Fly Tampa and Orbx sceneries are working as designed and it seems to me that what you are attempting to do just can't be done in a simple way. I guess you could try creating your own exclude file for autogen over the airport area. Not sure which tool you'd use for that in v5. All the best, John
  8. Hi there, Missed this when posted in August. To be honest as far as I can see this is hopefully a situation where Orbx SCA is the solution not the problem. I have the Fly Tampa scenery installed in P3Dv4 - it should be very similar in v5. I suspect you have disabled the following three KLAS files in the FTX_NA_SCA05_SCENERY folder of the SCA scenery. Usually doing this would be good practice but here, since you want to alter the Fly Tampa scenery, it isn't! If I'm right and you have disabled these files try re-enabling ADE_FTX_SCA_KLAS_CVX.bgl As far as I can see that should fix the problem. Disabling the Fly Tampa photoscenery here's what I see with all Orbx scenery disabled. Here's what I see with SCA active but the 3 files I mentioned disabled. Here's what I see with ADE_FTX_SCA_KLAS_CVX.bgl re-enabled in the SCA scenery. Basically the photoscenery is an integral part of the Fly Tampa scenery. It comes with it's own autogen designed to fit in with the airport and will suppress any autogen associated with the underlying land class scenery. Disabling it means the underlying autogen is no longer excluded. The file ADE_FTX_SCA_KLAS_CVX.bgl is the one which does that excluding job over the airport area in the SCA scenery. Outside the airport perimeter you will see some autogen conflicting with the Fly Tampa custom buildings - that is an unavoidable consequence of turning their photoscenery off. In summary try the following. Make sure the Fly Tampa scenery has a higher priority than SCA. Make sure ADE_FTX_SCA_KLAS_CVX.bgl is enabled. Disabling the other two KLAS files in the SCA scenery probably doesn't make any difference but remains good practice. Hope this helps. All the best, John
  9. Hi Bill, I do remember that, before being invited onto the team, Kern Valley seemed more susceptible than most to being tinkered with. Doesn't help I know but, in the small print, SCA is listed as a requisite. I understand your point about not wanting other airports compromised. I usually just moved any conflicting files out of the Orbx scenery area. Sorry I can't be more help. All the best, John
  10. Hi Bill, This airport is supposed to be an addition to the SCA regional scenery. Do you have that installed? Before my time as a tester and just had a quick look in P3Dv4 but I suspect that might be the issue. All the best, John
  11. Glad it's working As I said we've seen MSFS do this before - but not recently. Should have thought of it sooner but the memory ain't what it used to be! All the best, John
  12. Hi guys, I think I finally found it. By turning online functionality off I managed to replicate the problem. Please make sure all the online functions are on. In the past we have occasionally found MSFS switching them off without warning. My bad, I tried switching photogrammetry off but forgot to check with the rest switched off as well. Here are the settings you should have. All the best, John
  13. Hi again, EDIT - see my next message, I think I found the problem so this post became irrelevant! All the best, John
  14. Hi there, I'm not seeing any problems at EGTR but it clearly looks like you have some grass areas displaying as pink. Here's what I'm seeing with SU7 installed. All I can really suggest is that you make sure you have followed all the steps outlined in the post below. All the best, John
  15. Hi there, Just to confuse the issue I'm not seeing this problem. MSFS is fully updated and EGHI is v1.0.1 Edit: my MSFS is the Microsoft store Premium Deluxe. I've tried with photogrammetry on and off. Have you tried Verify Files for EGHI in OC? All the best, John
  16. Hi Max, Thanks for the feedback - glad you like the airport. I was worried that the lights themselves were appearing late but I see what you mean - the posts holding the lights appear quite late. Part of the never ending compromise between detail and performance which, as Doug indicated, will probably be even more of an issue with XBox (or so I'm told I'm not an expert!). Edit - forgot to mention. Only Matteo could give the full details but as far as I'm aware he has used custom objects for pretty much all the buildings on the island rather than relying on autogen. This gives a great feel to the scenery but does, I'm sure, have performance implications especially if everything was visible from too far away. All the best, John
  17. Hi Finn, I just tested this and, yes, these two work with the A320. I finally dug out our old testing reports and suspect the absence of the rest of the GSE was by intent (conflicts with the extensive array of static GSE) proving once and for all what I said earlier - my memory ain't what it used to be! Apologies for not checking the details earlier. So apart from the missing atis things seem to still be as intended. All the best, John
  18. Hi there. I can confirm what you are seeing. I know that in testing some were getting atis, some not and suspect that was never resolved. Since then I think we've found that the name of the atis in the 'afcad' file has to be the same as the airport designator (ENTO) so maybe that's the problem there. Not sure what's happening with GSE. As far as I know the gates are designated as Ramp GA Large which usually allows the full array of Ground services to be available. I tried in the airbus and can confirm that they aren't. I seem to remember that during testing they were there but my memory ain't what it used to be! I'm not using any mods. All the best, John
  19. Hi Jacob, Just to add to what Nick has said in testing we found that the texture resolution setting was the most important. I have an 8GB video card and was finding that with both Cityscape Brisbane and YBBN v2 active setting this to Ultra (4k textures) would usually end in a freeze and ctd so, in the first instance, I'd have a go at altering that. With it set to normal I never encountered a problem. Either scenery on it's own was fine at the higher settings on my machine. Been simming since FS5 and still wait for the day when I can run areas of heavy scenery with all the sliders to the right :-( When testing in P3Dv4 I found the frame rate simply dropped when the hardware was struggling with the settings. Hope this helps. All the best, John
  20. Sorry, I just saw this thread. Not that I can be of much assistance I'm afraid. As far as I know the basic problem is that the autogen used in photoreal sceneries like the TE range is the sort which can be created and edited with the annotator from the SDK and, as I understand it, this sort of autogen can't be excluded in the way that the autogen used in landclass based scenery like EU England can. As you've found a normal exclude won't manage it, even if you enable exclude autogen. I've never used ScenProc but am not aware of anything else which allows this to be done I'm afraid. With the UK2000 sceneries from what I can remember Gary used a photoreal background image but didn't have any associated .agn files in the texture folder. That's why you don't get autogen appearing on his airfields with the TE products but you do get an area around them where no autogen appears. All the best, John
  21. Hi there, The other thing which usually works is to go back to the main menu and start the flight again (don't change the airplane). I've seen this at quite a few airports and eagerly await an MSFS update to fix the issue! All the best, John
  22. Thanks for your kind comments but take the point - landmarks were always about enhancing the scenery rather than producing new airports so didn't make it an issue. Maybe should have done. That said, there are a few landable helipads in the scenery if you fancy trying them. In testing I found it great fun. In terms of flying I'm working on it but controlled crashes are the best I'm managing at the moment! A couple at the hospital The ASB building Cruise ship Support vessel All the best, John
  23. Me too. I've just checked back to our testing reports and the localizers were working fine then but aren't now. I'm wondering if ASOBO fixed something in an update which broke something in the scenery. It wouldn't be the first time! I need some more time to check up on the information I've got but will then raise it on the development forums. I'll let you know when I do. Apologies to Blanche - I must have missed his original post. All the best, John
  24. Thanks for confirming that Dave. I've raised the issue on our private forums but no promises. It's an issue I would definitely like to see working properly. All the best, John
×
×
  • Create New...