Posts by lastromantik

Well, this is simply brilliant!!!т

Okay, okay) I'll try to get back to development as soon as possible. For me, everything is born on enthusiasm alone, so there are no strict limits in supporting the project.

I'm glad that my work is useful to someone)

Hello, I haven't fixed any issues yet. I need to get back to supporting and developing this editor somehow. I'll try to fix what you're asking for in the near future.Thank you.

Quote from Muonstos

krpanotools64.exe and krpanotools32.exe

Now it's clear why it doesn't work) Here you either spend the night and remove 32 or 64 or use the new version of krpano

Quote from Muonstos

I have a licenced krpano but it's the 1.19-pr14 and your app it on the 1.22.

The script does not contain any krpanotools files. it only runs krpanotools.exe, which is located next to it.

Quote from Muonstos

Now it's working but I have a lot of watermark on the final file. Is it normal ?

It's because you're using an unlicensed krpano, maybe.

Or the tiles already contain watermarks and the script will not help in this case )

The complete panorama will appear next to the folder containing the sliced tiles.

Quote from Muonstos

doesn't detect the panorama path in the _settings.txt file.

The file must be named without underscores.

But I came out with an update on GitHub,in which I added automatic detection of the necessary parameters by the folder that needs to be transferred to the script itself. In this case, there should not be a settings file nearby. Check the new version

Quote from Muonstos

Hi, I've tested your app, but it doesn't detect my krpanotools.exe located next to it.

Hi, did you put the script in the krpano folder, next to krpanotools?

I would appreciate feedback on the script's performance, bugs found, and other annoyances... )))

check this out...

GitHub - LastRomantik/reMultires: Krpano script for assembling panorama from sliced pieces of multiresolutions

Krpano script for assembling panorama from sliced pieces of multiresolutions - LastRomantik/reMultires

github.com

Quote from Fernando

Yes, please. thanks very much

sent you to telegram

Hi, just yesterday updated my script for assembling panoramas from sliced pieces))))))
Message me on t.me\lastromantik ))))

P.S.
Maybe if everyone needs it, I can create a page here and post it for general use )

Try this )

Quote

Also I noticed that some hotspots are not saved. I remember making a link both ways and then only one way is saved.

Yes, this problem is known. and it was the reason for me to start writing my own web editor that would take these errors into account )

Quote

Interesting... but still would like to have it right in native krpano

I'm making an editor that fully replicates the functionality of the native editor, and makes the process a bit more convenient and faster )

I think Klaus is watching carefully and may add some ideas to the native editor to speed up work in it)

Quote from Coldmami

Am I doing something wrong? When I add hotspot to next panorama, then I click Edit 3D transition.

Is there a reason why arrow on next panorama is always looking forward, not backward? Since all panoramas are having the same heading, when going from pano 1 to pano 2 straight North direction, then link from pano 2 to pano 1 must be straight South but by default its also straight North

Perhaps you are doing something wrong in the process itself. Try my uhta3d_editor.

In it I tried to make the entire linking process as convenient as possible)

Or like this:

// initiate a variable that can be used to control the entire tour
let krpano = document.getElementById("krpanoSWFObject").get("global");

// call the scene load function
krpano.actions.loadscene('scene_name', null, 'MERGE', 'BLEND(1)');

Yes, you can add the type of devices to which it will be applied to the scale attribute:

<hotspot name="p1"
 scale = "1"
 scale.mobile = "3"
 scale.touch = "5"
/>

and so on... you can read here

As far as I remember in the quest, if you do not use the controller, the dot automatically appears.Although I could be wrong