kjjj11223344

It sounds like you are not shift + left clicking, which is required to select tiles. I should have made this more clear in the video.That zoom level message is more a warning than anything. The program automatically sets the zoom levels to be equal to each other, I should make that more clear.

Yes, right now the program does nothing with mesh. So there are issues wherever the default coastlines are incorrect. I decided to implement water masks in the inf files for resample such that default fsx terrain appears whenever there is water according to OSM. Unfortunately, if there is no water in fsx, then default fsx land will appear instead. I will implement an option to implement water masking by adding wave animations in the future. The mesh thing I might look into in the future as well, I am just very occupied with school now unfortunately. Any help with coding would be great 😉. There is actually a DLL the program relies on that is written in C++, if you want to play around that and make it better (I am currently not happy with the night texture creation results).

Are you making sure to tick the build for esp option? Also, there is an error in your path to resample. It should look like this: C:\\Ortho4XP_FSX_P3D\\resample.exe (You had two "C:\\" before).

I've been very busy lately with school lately, so apologies for the late response. That error you describe was reported by an earlier member, but I have yet to go around to fix it. I think it has to do with the order in which certain buttons are clicked. I also want to fix the night textures as the current output slightly differs from what FSET makes, and I think FSET night textures look better.

Is Ortho4XP actually throwing that ImageMagick wizard error? If you run magick wizard: wizard.jpg, etc. in command prompt manually, it will attempt to run ImageMagick on a file called wizard.jpg. If you don't have this file, it will throw that error (but this has nothing to do with Ortho4XP 🙂 ). As to the other error which states that the Providers contains invalid code - that is a small issue that is happening with the latest version of Oscar's original Ortho4XP code. I bring in all of Oscar's latest changes whenever he adds anything to the original code, to make sure the Ortho4XP for ESP can function exactly like the original Ortho4XP when it comes to XPlane. In one of his latest changes, that error was introduced. I haven't bothered looking into it nor fixing it, because it doesn't seem to affect creation of tiles. I am sure Oscar will fix it eventually :). To conclude: I don't believe either of these two errors led to you not having an Addon_scenery folder. Can you take a video of your workflow when running the program, so that I can spot the error?

Can you take a screen shot of of the command prompt output? Or copy/paste the output into paste bin. Are you using the latest version I uploaded around 7 hours ago? It worked fine on my machine, but as with any new release, it might have introduced bugs for others.

The night creation scripts are a work in progress. I ported the C# code that FSET uses for its night creation scripts into a c++ dll. It should be the same output that FSET uses, except for one part of the code that I had to modify slightly. I am currently double checking with what FSET produces and seeing if my logic differs too much from its algorithm (which I thought was pretty good when I used to use it). If it does, I will then port FSETs night creation logic fully into c++ with none of my modifications. Also - the amount of resample processes that spawn can now be controlled in the latest version. max_resample_processes In Ortho4XP.cfg controls how many resamples will launch at a time.

The strange coloration is due to the source you use. If you zoom into google maps, you will see that at high zoom levels, there is a wide variety of colors for certain areas (not visible on google maps if you use more zoomed out levels). I suggest trying another source. I tend to use Bing whenever google maps has inconsistent colors.

Yes, please see here: https://github.com/stackTom/Ortho4XP_FSX_P3D/tree/master/dist You don't have to download the whole repo again, just the ImageMagick-7.0.8-10-Q8-x64-dll.exe installer file. You can also get this file from the ImageMagick site, but I decided to include it in the github for convenience.

Unfortunately, yes. Resample is incredibly slow. I'm going to work on making resample work in parallel when I have some more time. Resample hardly uses up CPU, so I will manually spawn multiple resample process at once so more than one bgl can be made at a time...

Interesting. I have seen on fsdeveloper forums some people saying that LZW compression on TIFFs makes resample run many times slower. Will definitely add multiprocessing to resample when I have some time ;). Is there any other way to speed up resample, or is it just inherently slow?

I've determined that the simplest solution is to install ImageMagick to avoid this error for now. I have included the correct installer inside of the dist/ folder. After that, creation of night and seasons should work without the error.

Not sure if resample can be sped up. I'm going to disable LZW compression on my TIFs, as well as look into spawning multiple processes of resample at once. I believe that putting multiple images into one BGL doesn't speed up resample, at least not significantly.

You make a good point. I always just run with "build imagery/dsf" but I should make it work as well if you already have a tile downloaded. By the way, you can't interchange XP and FSX/P3D ortho photos, or masks. Also, mesh isn't supported for FSX/P3D currently.

You need to press "download imagery". If there are no files inside of "Ortho4XP_FSX_P3D-master\Orthophotos\+50-010\+51-001\BI_16", it means that no ortho photos have been downloaded. Tiles made for xplane arent compatible for fsx/p3d.

Yes, that is a new error message I added. I can't reproduce this, as ESP_build_dir *should* be set by the time that area of the code runs. Can you take a video of the steps you take to run the program? You mention that there are no files being made in "Ortho4XP_FSX_P3D-master\Orthophotos\+50-010\+51-001\BI_16". This confirms my suspicion that the file downloading code isn't being run (this is the code that sets the ESP_build_dir". Are you running the program like this: ? If not, then how are you running the program (I'd like to add logic to prevent this error in case others are running the program in the manner you are running it).

What python version are you using, and what error are you getting when you run it with python? Sadly, I built a custom c++ DLL (the pyd file in the main directory) as creating the night and season textures in python was too slow. This DLL only runs with the python version that I built it for (3.6.4), so if you want to run it with python, need to rebuild the DLL. There are rudimentary (and I admit bad) steps on how to do this on the readme.

Hi, I just updated a potential fix. I have not seen this error before, so if the fix doesn't help the issue, can you upload a video of the steps you use to run the program? Do you run the exe, or do you run it with python, and if so, which python version? If the fix fixed the issue, please let me know as well.

I am reading up on the ImageMagick documentation to see how to fix this issue with their library. Busy with work this week, but will post back once the issue is fixed (It is difficult for me to debug this as I dont get this issue on any of the computers I have tested the program on, and the issue seems to occur on only certain computers). I have seen online that installing ImageMagick should fix the issue. If you want, you can try that. Otherwise, disable creation of night and seasonal textures and it should work until I get this issue sorted out.

I added a potential fix to the code. Can you two download the latest version and let me know if it works now? The fix is based on what I read about the error form the ImageMagick documentation. If it doesn't fix it, I will continue trying to find a solution.

Hi, please install it, then run ortho4xp and see if it fixes it. If not, then I will post back once I see what this error from imagemagick means. Edit: Actually, please don't install it for now. Please download the latest version from github, and see if you still have the error. This way you can help me try to fix the error so that others don't have to install Imagemagick (if that is even a fix to this issue).

Very weird. You are getting the same error from imagemagick: Caught exception: Ortho4XP_v130.exe: RegistryKeyLookupFailed `CoderModulesPath' @ error/module.c/GetMagickModulePath/665 I will need to see what this error means and how to fix it. It only seems to appear with some computers with the ImageMagick library.

Does this have any advantage other than simplifying the inf files? I did it with bmp as that is how FSET did it, and I am not very familiar with geotiff's ;).

Yes, the error is with the c++ port of the FSET masking scripts i ported over. I use the ImageMagick library for that, and there is some reason why the image magick library is not working correctly on your system even though the version included in the .exe seems to work on other systems. Can you try installing imagemagick and see if it works? It is okay if you don't want to, but if you do, here is the link https://www.imagemagick.org/download/binaries/ImageMagick-7.0.8-9-Q8-x64-dll.exe

What do you mean?