RESOLVED SAK SP4 - Lon W141deg Mesh anomaly - still have some odd things happening

[Jethro VH-JET]

Hi Holger,

 

I was wondering if you could take yet another look at the Mesh anomaly along length of the Lon W141^o. My SAC installation included SP.003 and I had set FTXCentral to North America before installing SP4.

  

In my FSX setup I am still seeing the Mesh unresolved beyond a 2km circle around my aircraft. Directly beneath and within 2km radius the Mesh resolves to blend quite well, where the distinct sharp elevation mis-match is smoothed out.

Coast lines around Icy Bay in the area to the south show this unresolved then resolved behaviour as do the YT Mountains and Glaciers heading Northward along the W141^o longditude.

There is also a new anomaly that has popped up in the same Lon W141^o vicinity of (19AK) from the Pacific Ocean and travelling Sth/Nth through Guyot Glacier and onwards. It appears as a thin high wall approx 5Km long which travels northward with the aircraft.

 

 

 

 

 

 

 

 

 

 

 

[Jethro VH-JET]

additional info: The new anomaly visible from (19AK) that has popped up is only shown as a dark trench when viewed from Icy Bay, when closer to the trench it pops up suddenly as a thin high wall approx 5Km long which travels northward with the aircraft.

 

 

 

[wulfbindewald]

A spot check around 19AK in different altitudes could not duplicate this anomaly.

Everything looks normal. I am using SAK SP3&4, FSX DX10, No Globals, no other scenery enhancer.

 

Wulf

[Jethro VH-JET]

Hi there Wulf,

 

Thanks for being the only one interested enough to respond, I'm beginning to wonder if I am the only one to have this anomaly. My setup is SAK SP3 initial installation into FSX, then this latest SAK SP4 followed by a reinstall of OrbxLibraries v141228, with nothing else in this region, sim was set to North America both before during and after installation Mesh Resolution is always set to 5 Meters per Orbx recommendations and SAK .pdf.

I was really looking forward to seeing Holgers amendments to this W141^o longditude, and not expecting a "Great Wall" where none existed beforehand. It had been slated for this SP and pinpointed in a post made some time ago and special noted in the SP4 .pdf.

 

I know you have been unable to replicate in your sim but, would you be interested in capturing a couple of pictures resembling the last 2 pictures in my #2 post.

 

Here are the co-ordinates just to make it easy. These are in decimal but you can still type them into your map co-ords

Picture 2: Lat N59.966545^o  Lon  W141.651954^o   Alt 28.5ft      Mag 310^o

Picture 3: Lat N60.056441^o  Lon  W141.869738^o  Alt 13731ft    Mag 6^o

 

I think I may have to reinstall SAK from scratch if all else fails.

[wulfbindewald]

Hi Jeff,

 

panning around the 2 add. locations do not show anything abnormal.

So I suggest to look at first to the Status file inside the FTX Central/tools/reporst/FTX reports installed for confirmation, then have a look into the scenery lib entries (insertion point still on the right position?) before SAK overall reinstallation.

 

Wulf

[Jethro VH-JET]

Hi Wulf,

 

FTXCentral Reports ( FTX NA SAK Southern Alaska and YT/BC V1.00 Patch 004 February 2015 ) only an indicator though, which correctly read SP3 before SP4 installation.  Insertion points are all correct as they were before. SAK entries are in correct location on the list, all other entries are correct priority. I'll wait for Holger to read through he might have some ideas before I go ahead and start reinstalling SAK, I'm in no great hurry these days.

[Holger Sandmann]

Hi Jeff,

 

I suspect that there's another terrain mesh file active that causes those issues. SAK SP4 replaces the file mesh_multiLOD4-11_FTX-SAK_W145-141_Chitina.bgl, in \ORBX\FTX_NA\FTX_NA_SAK07_MESH\scenery. That file is definitely "clean"; I've checked in TMFViewer.exe and also see my screenshots below. Thus, if the file on your system has a Jan 2015 date stamp then you have the correct version and a re-installation of SAK probably won't help.

 

I've tested with both just SAK and SAK plus PILOTS Global FTX mesh and Global Vector, with the same result.

 

The fact that there's a transition from the correct elevation data to something else at some distance from the aircraft (meaning lower LOD values), and moving along with the aircraft, also indicates that another file is interfering. If it's compiled at the same resolution then the sim might get "confused" and load both at the same time.

 

Does the "wall" disappear if you temporarily deactivate the FTX_NA_SAK07_MESH entry in your scenery library menu?

 

Something else to keep in mind is that the "wall" doesn't necessarily have to be a terrain mesh issue, it could also be some rogue flatten or water polygon. However, the fact that it moves along with the aircraft makes a LOD-driven terrain mesh file the more likely culprit.

 

Cheers, Holger 

[Jethro VH-JET]

Thankyou so much Holger,

I knew you would jog my memory on conflicting mesh.  "Problem solved", silly me forgot that only before Christmas I was experimenting with (RaimondoTaburet 38m mesh for Alaska) in an area I thought was outside SAK/YT in a default Alaskan area, and had placed it in an active Mesh folder along with some other Low grade Mesh, completely forgot I had placed it there. Oh how embarrassing!       

Disabled/removed it and now, all is fine once again. Even the other anomalies noted in my first post have disappeared and are looking superb once again. 

 

Please accept my apologies, mark this Topic resolved and bury it deep in some dark corner.