Search Unity

  1. Unity 6 Preview is now available. To find out what's new, have a look at our Unity 6 Preview blog post.
    Dismiss Notice
  2. Unity is excited to announce that we will be collaborating with TheXPlace for a summer game jam from June 13 - June 19. Learn more.
    Dismiss Notice
  3. Dismiss Notice

Question Standalone app only working on development PC [Win 10]

Discussion in 'Windows' started by Brko_Photogram, Jan 17, 2024.

  1. Brko_Photogram

    Brko_Photogram

    Joined:
    Jan 20, 2021
    Posts:
    2
    So here is my problem... I've built an interactive 3D map, and I've placed a folder with content to be accessed through the map, in the app directory (same level as .exe file).

    It works fine in the editor, works fine from any drive on my computer after the build, but when I copy it (the whole standalone App folder of course) via stick to another PC, it won't spawn the pins (prefabs) which you click and they show the content. Or better said, it seems to spawn them, but doesn't show anything on the map.

    upload_2024-1-17_14-56-29.png

    I'm spawning this kind of animated pins which are clickable and open popup with content from the folder (images, 3D model, text etc.)

    So the logs in the standalone app show no errors, and my debugging has shown this:
    1. The content is read by the app (.txt files with coordinates for the pins and names)
    2. And after instantiating pins, I count them in the script, and log says there are exactly 4 pins as there should be! But I don't see anything on the map!

    Again, all is spawning ok on my development PC [win 10], but not on other PCs [Win10 and Win11]
    The app besides this runs smoothly on other PCs, I can navigate the map as it should be, just the pins aren't showing.

    Any ideas? Maybe the pins models haven't loaded into the build or smth like that?
     
  2. Brko_Photogram

    Brko_Photogram

    Joined:
    Jan 20, 2021
    Posts:
    2
    Ok so figured out the problem!
    For some reason, .csv file with coordinates is being read differently on another PCs! So the coordinates are completely different.
    For example instead of 47.3, 56.7 it reads 473.0, 567.0.

    Still haven't figured out why.