BOX NOT PROCESSED

[fdomatias]

Hi, I've recently encountered these issues while processing some areas. There are areas that aren't processed, leaving a default box. When I test it in Prepar3D, I see an empty square, as if it hadn't been processed. What's causing this problem? Here's an image.

#--- Partial FS Earth Tiles ini datas ---

[FSEarthTiles]

AreaDefinitionMode = 2Points
NorthWestCornerLatitude = 37deg 3min 9.25sec north
NorthWestCornerLongitude = 116deg 21min 20.43sec west
SouthEastLatitude = 35deg 54min 12.34sec north
SouthEastLongitude = 114deg 38min 59.31sec west

[stackTom]

Weird. Can you try with a different tile server and see if it occurs?

[fdomatias]

I've tried several and the error is the same. This is in the Las Vegas, NV area, but it also happens in European countries, where unprocessed squares remain. I tried version 2.10 and below, and the same thing happens.

[fdomatias]

I even tried it on my laptop and the same problem exists, that is, I tried it on two computers and the same error.

[stackTom]

My development machine is down at the moment. But can you try this original release: https://github.com/stackTom/FSEarthTiles/releases/tag/v1.1

I should be able to bring my machine up in the coming days. If you could try with v1.1, let me know. If it works, you can stop testing. If it doesn't work, please try with different zoom levels (zoom out ideally) and let me know if that works.

[fdomatias]

I'll try what you're telling me, and I'll let you know more details. Thanks.
It's very strange because I was able to do it without any problems two years ago, but now I'm trying to do it again and I'm running into that error. I'll keep you posted.

[fdomatias]

[fdomatias]

Similar problem in v1.1.

[stackTom]

Can you send me your FSEarthTiles.ini and FSEarthMasks.ini?

[Dave2907]

Hi, Were you able to resolve this?
I am having a similar problem, I have tried different servers and FSET versions with no effect.

With the above the two areas there was no error messages, however I do also get the below in others.

Thanks,
Dave

[stackTom]

The error message means there is an error in the FSET data for that tile. I usually look at the data and fix the error in OSM so everyone can have it (sometimes it's a typo etc).

The unprocessed box error is different. I haven't looked into it yet. Will try in coming days. Can you try running FSET only on the part that's failing and tell me what happens?

[Dave2907]

thanks about osm error.

i have tried running fset 'box within a box' to no effect. i have noted that on my original attempt that islands within lakes have been processed. see my attached screenshot.

[stackTom]

That's very strange. I'll have to setup my FSET development environment and see what's going on. I'll look at it in the coming days.

What happens if you view the generated bgl files in TMFViewer?

[Otter999]

I just rendered this scenery. Nothing wrong there. BTW, I did whole of Europe and never encountered such a glitch. My guess is the user has some scenery for Las Vegas activated or a wrong scenery order or something is messed up with ORBX Vector, elevation data etc. etc. that interferes with the correct view of the photoreal scenery. I would check the scenery library for all these areas in NV and Europe and start by deactivating everything except the photoreal scenery.

[stackTom]

@fdomatias @Dave2907 can you try @Otter999's suggestions and report back? I've also never experienced these problems before. Try to disable those things that @Otter999 mentions.

[fdomatias]

@stackTom Hi Again, I don't have any ORBX products installed, nor any paid or additional scenarios. Just the created Photoreal, nothing else.
This is experienced in some locations and happens occasionally. Last year, for example, I tried Belarus, and it failed in the capital. Three months ago, I tried again and it worked without any problems.

Las Vegas too. When I reported it, I had the problem. Now, a month ago, I tried again and it processed without any problems. What I'm experiencing is strange.

I'm currently viewing Finland, and there's also an unprocessed area.