Jump to content

kjjj11223344

Members
  • Content Count

    1,053
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by kjjj11223344

  1. I am not sure what this error is to be honest. I have had issues in the past where running the program via python (and not the exe) would fail with missing DLLs if .net framework isn't installed. Maybe try installing the .net framework and see if it fixes the issue? Although, i have tried running the program on PCs without .net framework, and it works as long as i run the .exe... .net framework install: https://www.microsoft.com/net/download/dotnet-framework-runtime Are your windows PCs fully up to date?
  2. Very weird. I have never seen this error before. Can you try running the program on another computer? It seems to be related to one of the dll's of Imagemagick, but it is working on all of the computers I tried the program on.
  3. Don't mind at all - your insight is appreciated :). I've been looking for the FSET code actually, to see how it implements its texture undistortion logic (I dissasembled and found the function, but he dissasembly is very difficult to understand). Do you know where I could find the code? Another reason I decided to work on Ortho4XP rather than FSET is I couldn't find the FSET code anywhere. I even contacted the guy who updated it to the latest version, but he hasn't even logged onto avsim in a long time, so he never got back to me.
  4. I have some questions to help me narrow it down: What OS are you using? Is it 32 or 64 bit? Are you using the exe in the dist folder, or running Ortho4XP_v130.py from the main folder using your own version of python? Are you mixing and matching files from the initial release and the current version of the program?
  5. Chris, I see what you are saying. I have used KMLs before to create scenery for my hometown. It took me approximately 5 days to draw the polygons for all the coastline, for the area in question in FSET. I wanted it to be detailed, but even after 5 days, the scenery I made isn't nearly as detailed as the masks Ortho4XP can generate (I am only human, after all haha). Also, I know there are programs to convert OSM data to KMLs, but my wish was to get it so that this could all be done automatically with the click of a button :), without having to use external programs, etc. I then had three options - write code to create masks from OSM data as Ortho4XP does, write code to create KMLs from OSM datato be used for FSET, or extend Ortho4XP to create inf files and call resample, etc. Due to my limited knowledge and skillset with OSM and KMLs, the last option was what I deemed easiest. The fork contains all of the Ortho4XP code, and I will be bringing in any new additions/bug fixes Oscar adds to the main repository of Ortho4XP, I am not copying Oscar's idea and doing it from scratch, as that would take way too long and would mean I would be better off going your suggested KML route :). In fact, my fork should work exactly like the main Ortho4XP if you want to create Ortho scenery for XP ;).
  6. Yes, that is my goal. Might take some time as my time is limited, but I definitely want to do it.
  7. You don't need to even have python installed if you are using the pre built exe. The first ERROR you see in the black cmd window is something new which appeared when I brought over Oscar's latest Ortho4XP code over. It is more of a warning than an error, and can be ignored (it occurs in the latest Ortho4XP from oscar's github as well). The "FSX/P3D bulding requires..." is a warning I added. Basically, if mask_zl is different from zoomlevel of the orthophotos, the program sets the mask_zl equal to that of the zoomlevel you choose in the dropdown. Again, this is more to let the user know what is happening, and it can be ignored. As to the program hanging and not doing anything - are you shift + left clicking on the tile on the map? Ortho4XP requires shift + left click rather than just left click. Edit: just tried it. Not shift + left clicking should be your issue.
  8. I created the fast_image_mask.pyd dll using python 3.6.4. That's the only thing I can imagine is going wrong. I suggest rebuilding the pyd. You need visual studio installed, as well as q8 ImageMagick++ dll's installed on your system. Then do something like this: "F:\ExtraPrograms\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.14.26428\bin\Hostx64\x64\cl.exe" /LD /I "C:\Program Files\ImageMagick-7.0.8-Q8\include" /I C:/Users/fery2/AppData/Local/Programs/Python/Python36/include /I "C:\Program Files\ImageMagick-7.0.8-Q8\include" src\cpp\fast_image_mask.cpp src\cpp\FSET_ports.cpp from the 64 bit visual studio command prompt (or 32 bit if your python and ImageMagick are 32 bit, but I have only tested on 64 bit). Alternatively, you can downgrade to 3.6.4 of python or use the prebuilt binary in the dist folder. Let me know if you decide to build and don't understand the above command. I just copied the command I used, but I suppose I could explain it more if it is unclear.
  9. Do you see a fast_image_mask.pyd in the main folder of the package? Also, does the binary inside the dist folder work, or does it give the same error (it’s okay if you don’t trust the binary and want to run it with python, I’ll still help you out). Finally, that ERROR in the first line is something new that happened after Oscar’s latest commit to Ortho4XP. It happens in the latest plain Ortho4XP as well, and doesn’t seem to affect anything (its more a warnig than an error).
  10. I suppose I could have created a program to create KML’s from OSM data which could be fed into FSET. But I’m not well versed in the format of OSM data nor KMLs, etc, and it is easier for me to make Ortho4xp support FSX/P3D rather than come up with the logic to create KMLs. I’ve seen tutorials about doing this with arcgis for example, but when I read about it years ago, I couldn’t figure it out + I wanted something which was automatic and didn’t require any user intervention. If there exists a programmatic/automatic way to do this OSM to KML conversion, please let me know, as my inability to find this isn’t why I created this fork in the first place :).
  11. Please download the latest package from GitHub, as the new executable contains the logic to handle these new settings.
  12. I have added support for creation of night and seasonal textures. To enable these, just change the below lines in Ortho4XP.cfg: create_ESP_night=True create_ESP_summer=True create_ESP_spring=False create_ESP_fall=False create_ESP_winter=False create_ESP_hard_winter=False from False to True accordingly. P.S. how can I edit the first post of this topic so I can write all updates there?
  13. Which provider is SP? I don't see it in ortho4xp v130 dropdown list.
  14. Should work in v3, as long as you have the correct resample.exe from the v3 sdk.
  15. The second issue is due to the satellite source you are using. I suggest trying a different source with more homogeneous coverage. The first error is strange. Are you using the latest version from the github? I fixed a bug which would cause this in the latest version. It is just strange that it is happening with ZL 17... the bug was only occurring with low zls previously. Will investigate. Currently in the process of adding night and season masks, will update the github when I'm done. Probably wont be for a week or so or more, as I am going on vacation.
  16. Do you mind posting a video of the steps you are following when trying to create the ortho scenery? It will make it alot easier to spot what the problem is :).
  17. I admit, that is very confusing. I will probably modify where the output ADDON_SCENERY folder is placed in the future because honestly, placing it inside the XP folders was just a quick hack so I could get everything working and start making sceneries...
  18. I gave up and switched to Ortho4XP v1.30 which generates masks for each downloaded satellite bmp at the correct zoom level instead of one large mask for the area at zoom level of 14. It is working fine now. I think the issue is that resample.exe needs the mask and the main image that is to be masked to cover the same physical geographic area.
  19. You need to change the ESP_resample_loc setting in Ortho4XP.cfg to be the path to your resample.exe from the P3D or FSX SDK. Make sure to insert double backslashes instead of single (so c:\\path\\to\\resample.exe instead of c:\path\to\resample.exe).
  20. Did you press apply after changing the settings on the settings page? Can you post the output of the black command prompt window that should open when you open the program.
  21. This is more a warning message than an error message. The program automatically sets the mask zoom level to that of the main tile zoom level, so there is nothing to worry about.
  22. https://www.youtube.com/watch?v=fkvmlbJXAq4&feature=youtu.be
  23. Aussibob - did you shift left click when selecting an area on the map?
  24. Also, does anyone have the FSEarthtiles source code? At 2m/pixel setting for example, it produces higher quality textures than ortho4xp at zl 16 (even though zl 16 is approximately 2m/pixel). I believe it’s because FSET has logic to resample the BMP images to produce the least distortion possible within the sim. Would love to port that algorithm over to Ortho4xp.
×
×
  • Create New...