Quantum Amiga

A few pics while having fun experimenting with the Beaver which I've migrated from FSX-SE to P3D v4.5. Also trialing out cloud shader mods for lighting orientated clouds. The Beaver, migrated and configured with McCoy water FX and A2A shockwave lighting. Now that the Beaver is installed time to trial both Beaver and cloud shaders. The cloud shader changes the lighting and look of clouds. Found some beached shipping while flight testing, I guess the AI is not expecting a group of islands ? Last one after takeoff @ 11S, highlights the cloud shader and the quite dramatic look it can generate. Cheers

Hi Greg, Details provided. Cheers

Hi Greg, Thanks for reviewing this issue. As per your suggestion I created a test flight for KMHT, set to summer with a date of 21/06/2019, then flew around a bit and found an area that looked a little devoid of trees. A check of the ContentErrors.txt logging showed the following. error=Texture VEG_BROADLEAF_CHESTNUTMAPLE_SU_TF_D.DDS failed to load (FE_REQUEST_STATUS==13) error=Texture VEG_BROADLEAF_OAKSYCAMORE_SU_TF_D.DDS failed to load (FE_REQUEST_STATUS==13) error=Texture VEG_BROADLEAF_THIN_SU_TF_D.DDS failed to load (FE_REQUEST_STATUS==13) error=Texture VEG_BROADLEAF_MESQUITEOLIVE_SU_TF_D.DDS failed to load (FE_REQUEST_STATUS==13) At this point I took 4 x copies of one of the palm tree textures and renamed as the above four files to act as easily identifiable test textures. Result with missing textures recorded in logging: Result using palm tree testing textures to replace the missing textures: Looks pretty clear cut. The Config I'm using is as per: I await Orbx's further advice. Cheers

Hi John, Yes logging is typically used when developing and in tracking down and resolving bugs as well as in customer issues, however I'm not about to be burying my head in the sand... I use logging extensively when tracking down customer reported issues and during development in web, client and server related issues, and I am aware software dev is not an exact science hence why there is QA and there is the availablity of logging. The way I see it there are 2 x possiblities. 1), The files are actually missing, this would be a bug. I see this in the QA of R&D releases where dependancies and various files are missed, the old adage "it works on my machine" but when packaged things are missed. 2), The files are not intended to be released in the package, however given the scenery is requesting non-existant files that would be a bug. And I gather there would be holes in the vegetation display given files are requested but are unable to be loaded. Still there is the issue of the config being regenerated as .off and .off.off what's that all about ? because it seems like enablement is not a possiblity at all. Cheers

More items. error=Texture VEG_BROADLEAF_THIN_SU_TF_D.DDS failed to load (FE_REQUEST_STATUS==13) error=Texture VEG_BROADLEAF_MESQUITEOLIVE_SU_TF_D.DDS failed to load (FE_REQUEST_STATUS==13) Has all the looks of a regression issue to myself (I do work for a software R&D company and reguarly QA releases from the dev crews). Cheers

I have it in P3D v4.5 and there were a bunch of things I had to do for nicer compatability. One item that was annoying were Pine Trees surrounding the area, which is simply not the case and is why I've switched off some of the AP files. The AP itself is an FSDG creation. There are some replacement textures available on the Aerosoft support forum and I downloaded a replacment AFCAD from the below location. Urmel’s AFCAD’S for Payware Airports (Prepar3d v4+v5) https://jcai.dk/ https://www.alpha-india.net/forums/index.php?topic=26287.0 And disabled the following files via .off AFX_YAYE.bgl.off LC_8240.bgl.disabled in favour of Orbx LC_8241.bgl.disabled in favour of Orbx RS_KataTjuta.bgl.off Uluru_Mesh_V1.bgl.off YAYE_BGLLights_New_FS9.off Fits in relatively nicely with Australia v2. There is also an OZx YAYE, which is quite different, though both have aspects of pros and cons and while ultimately both are an improvement over nothing, neither are anything to write home about. In reality both are quite long in the tooth and origionaly released for FSX. I'd really like a new release of YAYE, one the encompases the entire area as HQ photoreal, would be great for sightseeing flights and for the jet airliner crew, would really showcase that part of Australia. I'm surprised Orbx hasn't considered such an airport and surrounding area, it's not as though there are loads of complex buildings etc. and it is a showcase area of Australia, e.g. jet to from Alice Springs to YAYE and GA sightseeing flights around the rocks. Anyway... here are a few pics. Cheers

Hey Folks, I was hoping if someone @ Orbx can confirm if there is an issue with the TF2 package. I ask because, while developing and testing gauge programing I noticed the errors below popping into the ContentErrors.log, quite a few in repeating runs flying from 11S. error=Texture VEG_BROADLEAF_OAKSYCAMORE_SU_TF_D.DDS failed to load (FE_REQUEST_STATUS==13) error=Texture VEG_BROADLEAF_CHESTNUTMAPLE_SU_TF_D.DDS failed to load (FE_REQUEST_STATUS==13 A review of the TF2 files shows sure enough I don't have them, infact there are only 7 SU (Summer I assume) textures compared to, 21 x Winter 24 x Hard winter 21 x Spring 58 x Fall 7 x Summer I did perform a verify and no changes to the file count. There are also a few entries in the orbx_cpl_TF2.xml that don't have the look of being quite right. The majority are, <onpath>TF_Common_Orig.BGL</onpath> <offpath>TF_Common_Orig.BGL.off</offpath> But there are a few that look like the below. <onpath>TF2_Common_Default.BGL.off</onpath> <offpath>TF2_Common_Default.BGL.off.off</offpath> Is there something going on ? Cheers

Tomato and Reshade to thank for such tuning. Actually the airstrip is not improvised, it's listed as N713 and can easily be found by installing the NZ NI unlisted airports pack. I landed @ N713 and taxied up to the buildings to have a gander so to speak. Cheers

Thanks everyone and yes, they were taken in P3D using an historical date (Spring) and weather of September 2019. I origionally purchased the NZ Islands back in my FSX days which was a huge improvement over the default FSX scenery. I remember those FSX days, a 2 core workstation with a NVidia 760 I bought second hand from a work collegue, the machine could barely keep up and I'd have to keep pausing and wait for the scenery to catch up. Now my OC Ryzen 3800x with OC 1070Ti manages to keep up with a very fluid 30 Hz vsync, although looking at updating the GFX card to a 3080Ti in a couple of weeks once I get my second vaxx out of the way. Cheers

After resolving my wierd North Island coastal irregularities, I'm taking a flight up the coast checking to see if there are any other issues that might bite. And so far all looking pretty good :-) Take off from Waihi Beach (NZWV) in my modded PBR Carenado C208B Caravan. Waihi Beach (NZWV) in the left background. North(ish) bound. Up the coast and left turn. Heading to Cascade Bridge (N713) Taking at break @ Cascade Bridge (N713), bit of a tough place to land. Tuning into NZAA Getting closer. Lining up for NZAA with a jet coming in behind me. Next will be back over to the East coast to Pauanui Beach (NZUN) then North to Matarangi Beach (NZAG), Springhill (NZSL) and finishing @ Whangarei (NZWR). Fingers crossed no wierdness pops out. Cheers

Just an update to this issue. I traced the prob to when I installed Flightbeam's NZAA. Flightbeam have their own managment tool for configuring their airports with a troubleshooter where it makes recommendations to disable selected Orbx NZNI items and provides a slider to do so. The slider simply adds or removes a .off to the target file. Upon review of the xml used to configure the airport I found the following items. <Troubleshooting> <Keyword>*NZAA*</Keyword> <Keyword>*4_mesh_multiLOD4-12_FTX-NZNI_section2*</Keyword> <Keyword>*0_excl_FTX_NZNI_GUID_all*</Keyword> <Keyword>*cvx_FTX_NZNI_water_9445_summer*</Keyword> <Keyword>*2_FTX_NZNI_orthoimage_NZNI_LINZ_ManukauHarbour_2m*</Keyword> </Troubleshooting> The "*4_mesh_multiLOD4-12_FTX-NZNI_section2*" section was origionally duplicated in the list above and I thought that might be the issue, however a test showed not so. The problem is introduced when "*0_excl_FTX_NZNI_GUID_all*" is disabled (via .off). I'm not aware of the file's design intention however if it is disabled it certainly results in those weird North Island coastline issues, assuming vector is installed. An easy fix via the Flightbeam Management tool by just sliding file's on/off switch to the left. However I also had to first navigate to the files directly and remove the duplicates created by running the Orbx Central verify files option. Just in case anyone else comes across the same or similar issue. Anyway onto NZAA to check if anything else is affected. Cheers

Hi Nick, Thanks for the confirmation. I cannot think of any 3rd party item that would be affecting coastlines, I do have a few Orbx and other 3rd party NZ airports though, and the orders of Orbx sceneries are as applied by Orbx Central with 3rd party above Orbx. The above said I did find a screen shot of Ohiwa harbour dated September 2020 where the coastline irregularities did not exist, and guess something between then and now has altered NZNI. Cannot recall of any specifics though. A verify of NZNI found 55 files needed replacing. 2021-11-13T22:13:47.760Z [DEBUG] [Central::SaturnDispatcherService] - Requesting download and install for product nzni from Saturn. ~ 2021-11-13T22:14:03.347Z [INFO] [Saturn] - [INFO] Required files: 55 2021-11-13T22:14:03.347Z [INFO] [Saturn] - [INFO] Required chunks: 5 And all good again, although I guess I'll likely find some of my Orbx and other NZNI airports will now need the same process applied. I'll make my next major flight an around NZ, landing at the various payware airports and keep an eye open for any changes now that I've a marker on the issue. Cheers NZNI coastline issues resolved.

It's Ohiwa Harbour about 8 nm West of NZOP

Hi Team, Can anyone advise on why I might have these New Zealand North Island coastline irregularities ? And just as importantly... how to resolve ? I do have NZ North and South Island and Vector but haven't noticed the coastlines being out of whack until recently. I did run the Vector Airport elevation tool prior to noticing but otherwise the Vector and NZ NI & SI remain in their order locations of when they were installed (NZ NI & SI and vector are installed into the sim root). Cheers

For ordering I have a marker folder to mark the top of the P3D entries. Orbx airports and regions go below the marker and Global openLC go below the Orbx airports and regions. Above the marker are sceneries and addons from other companies. I also have a mix of the Orbx sceneries installed into the sim root and as xml addons and use the Lorby Addon Manager to exclusively manage the scenery and addons as I've found the P3D xml addon manager to be totally buggy once things get complex (I have 211 xml packages and 25 autodiscovery xml locations configured). If using the OZx YMBD the following two Orbx files files should be set to .off FTX_AUS_YMBD_objects.bgl ADE_FTX_AUS_YMBD.bgl I do have Australia v2 installed into the sim root which means the region is added to the scenery.cfg rather than the add-ons.cfg And I do recommend the Lorby Addon Manager as it is more reliable than P3D's addon manager, plus has helped myself track down ordering issues causing similar types of issues. The above said maybe there is something left over from Australia V1 ? assuming it was previosuly installed. If you cannot solve the Orbx support crew might want you to upload copies of the scenery.cfg and add-ons.cfg for review. Cheers

Order of scenery maybe ? What version of P3D v4 is being run ? I ask because LM made changes to the way airport elevation is handled in 4.5 HF2 I believe, I'm running 4.5 HF3 or version 4.5.14. I can say I have both the AusV2 Orbx default and the OZx version and both are displaying correctly (as in if I enable one or the other), although I prefer the OZx one. I use Little Nav Map to display the airport bgls for easy ID as to which files are used to create the airport. Orbx YMBD OZx YMBD Little Nav Map - showing the bgls in use (LHS just above the flight plan altitude display) One last pic of flying over the town, I actually did some work for MurryBridge Council a few years ago where I installed their EDRMS (Electronic Documents and Records Management System), never been there though, all the work was performed remotely.

Wow, when you see those avatars they just scream next gen GFX. The good old Orbx originals back from the FSX days just no longer cut it, but you do have to take into account the software and hardware capablities of the day. However it also highlights the issue of a lack of ongoing improvement due to the original platform of FSX being essentually stuck in time, thus a product was always a bake once, release (with a few bug fixes along the way) then forget. Good for profitability but stuck in time. It also brings the problem of product compatablity (with P3D) where compatable does not nessecarily mean improved. I guess what with the base GFX bar now having been set quite high and with MSFS being continuosly improved, so too will developers need to also start investing in continous improvement of products. The software developement company I work for has a %25 yearly premium for support and maintenance which helps fund ongoing improvements and new developement, plus subscriptions are another method also in use to keep steady funding flowing. Now for the horror BBQ I would never like to be stuck at.... :-) But then again there are some quite detailed scenes in older Orbx scenery. Cheers

Mine is for ikbenik

REPUBLIC F-84 F THUNDERSTREAK over Orbx Florida True Earth I'd taken off from the Space Shuttle landing airport. Cheers

Giday, You're not flying too fast for the scenery to keep up perhaps? If the sim is paused does the scenery catch up eventually ? 2560x1440 is what I use for a DSR screen mode and my 1070ti manages the resolution Ok, provided I don't exceed a GPU load of about 97% A FFTF value only functions when the sim internal limiter is not set to "Unlimited" (I always run Unlimited and use FFTF Dynamic). You could try an affinity mask to set P3D running on the cores only of the first... say 4 processing cores (and running on both the cores and threads for the remaining) and see how it goes. Another thing I have is a highly optomised Sim/Orbx install on an NMVe drive rated at a read rate of ~3500 MB per second. Additionally the Orbx libraries live on a Ram Disk for maximum speed of loading. Everything happens really quick. Sorry my p3d config file itself is v4.5, that said the link below is a thread covering a selection of settings I use that you can trial out and see what suits. https://www.avsim.com/forums/topic/604850-textures-appearing-black/ Cheers P.S. came across some good mil jet freebees. Flying over Florida True Earth @ 345 Knots,

Certainly adequate hardware, mine's a Ryzen 3800X and a 1070ti, and yes both are overclocked too. 4.5 Ghz base for the CPU and 2 Ghz for the GPU. What are your's clocked at ? 30 fps shoud leave lots of headroom for GFX slider ramp ups. What's the screen resolution ? I have 1080 x 1920 and use DSR (Dynamic Super Resolution) to fly at one step down from 4k, cannot go any higher in general use as it overloads the GPU (need a 3080ti - if only they were not so expensive...) Trialled disabling HT ? I have SMT disabled on my CPU (AMD's version of HT) as I found P3D performed much better, and my CPU ran a lot cooler, or you could trial using an Affinity Mask to place P3D on cores only, I did trial that too but found SMT off was the better performer. There's a thread on AVSIM - https://www.avsim.com/forums/topic/606021-affinity-mask-word-not-alloweds-guide/ I do use FFTF Dynamic to manage the scenery loading when the frame rate in sim is set to unlimited. FFTF Dynamic basicaly controls the P3D FFTF value in a dynamic way, either by height range or FPS range. It sounded like snake oil when I first came across it, however I had a saved scenario where the scenery was always blurry at a particular point and FFTF Dynamic prevented the scenery becoming blurry, so yeah it works for myself. I also have a number of prepar3d.cfg options applied to tune the configuration to my usage. You know, stop building textures unloading and loading, an affinity mask, smoother cockpit shadows, higher lods for vegetation, and maxing out the autogen. All are settings outside of the UI options. I'd be interested to hear how you go with some trials. Well thanks, more pics at Screenshots and Prepar3D, and some vids Oz Sim Pilot. Cheers

Where is the B24 from ? Cheers

Giday, Usually scenery display will depend on computer power vs. fps desired. What's your hardware specs and what sort of fps are you getting ? I limit mine via a 30Hz vsync which gives a smooth 30 fps while leaving CPU and GPU reserve power for ramping up the settings for scenery and whatnot. Since the CPU and GPU are not trying to operate at maximum fps there is reserve power to maintain a stable 30 fps and increase the gfx settings and radius etc.

Various shots taken in P3D with my new Ryzen 3800x CPU, which has made quite a noticable improvement over the previous gen 2700x I was running. Basics were a BIOS update and drop in the new CPU, then tune the base clock rate to 4.5 GHz and disable SMT. A sweet running CPU giving great sim flying. Heading towards Skagit in the Ant Tigermoth Pro. Turning towards parking @ Goheen airstrip It seems no matter when I fly there is always weather, and here I'm heading into the weather and then out again while flying North from Goheen. Another weather one, flying east from Sekiu 11S airport, had to keep low on that flight. My B120 Embraer, I just installed 15 liveries, my GTN 750 and performed some xml work in the model and gauges to cleanup a few bugs that were annoying me. My A2A C182, where I've been neglecting maintenance and a flight in NZ nearly ended with not making the airport due to the copious amount of smoke and rough running of the engine, but hey got there in the end... represented quite a fun challange to coax the aircraft to keep running while loosing as little height as possible. Same C182 @ Cushman Meadows on a misty day. The Goose Redux @ Lake Trillum in Oregon USA Same Goose and same lake while tuning the contact points for new water wake effects. That's All Folks ! Cheers (and about to enter another 7 days of snap Covid lockdown).

I've found YBBN v2 is very demanding on system resources, my 8 GB 1070Ti normally sits at ~5 GB, YBBN takes it to almost the full 8 GB and 100% use (and my GPU is clocked to 2 GHz). That said I can do 30 fps around the AP provided I detune settings to free up the GPU resources, otherwise the GPU maxs out with a subsequent frame rate drop and is thus stuttery. I would imagine a 3080Ti would handle it Ok though. Cheers