PDA

View Full Version : FGU LOS Tool produces not working occulus data



Waldbaer
January 3rd, 2021, 02:21
Hi guys,

I have difficulties to understand why the LOS tool produces almost the same output with LOS data but not with the right dots etc. This said it leads to the fact that the data would be corrupt and does not show up correctly (s. screenshot; left side is the original and rigth side produced from the LOS program). The campaign was created in FGC and then I loaded the module in FGU - created the LOS data and then used the LOS tool which produced the corrupted data attached. Please help - it looks like just the dots are wrong but this nevertheless produces completely different results.

Thanks for your help in advance!

Zacchaeus
January 3rd, 2021, 09:46
Are you saying that the final map when you test it has the incorrect occluders? I've looked at a couple of my moduledb files and compared them to the occluder files produced by the tool and I can't see any kind of commonality between the two (although it's difficult just looking at a mass of numbers on two files). Nevertheless the maps have the correct occluders on them.

Waldbaer
January 3rd, 2021, 15:19
Yes, that is what I meant. I'll share screenshots as soon as I am back at my computer today (I could share the module, too, but would better send only via pm in case you want to look at it yourself). Maybe it has something to do with the map itself and zoom etc.? Because due to whatever reason the map starts very small when I first open the module with FGU. However, I come back to this asap. Thank you for the assistance so far.

Waldbaer
January 3rd, 2021, 18:38
Are you saying that the final map when you test it has the incorrect occluders? I've looked at a couple of my moduledb files and compared them to the occluder files produced by the tool and I can't see any kind of commonality between the two (although it's difficult just looking at a mass of numbers on two files). Nevertheless the maps have the correct occluders on them.

Please see the following two screenshots: "LOS defined" shows how I defined the LOS in a brandnew FGU campaign. "LOS after extracting" shows how it looks like if I use the module where the tool copied the XML for the LOS data.

I have an assumption what happened here: I exactly followed your description in the dev guide which sais that I should point the tool to the moduledb folder. But I do not have this folder because I opened the assets of the module and then created a new entry within images also exactly like described on the dev page. I believe it will be better if I work directly within the open module without creating a separate entry image within the campaign and thereby create the moduledb folder. This will be better I believe. For now the tool used the db.xml which seems not to work as precisely.


4250142500

Zacchaeus
January 3rd, 2021, 19:25
Clearly that isn't correct. I'm not sure what the problem is - I haven't experienced any problems using the extractor tool. I'm assuming that you are creating the files from the moduledb folder in the Unity campaign that you created the LoS data in, and injecting the data into the Classic campaign/images file and then exporting the module again from Classic and testing in a new campaign in Unity?

Waldbaer
January 3rd, 2021, 20:14
Clearly that isn't correct. I'm not sure what the problem is - I haven't experienced any problems using the extractor tool. I'm assuming that you are creating the files from the moduledb folder in the Unity campaign that you created the LoS data in, and injecting the data into the Classic campaign/images file and then exporting the module again from Classic and testing in a new campaign in Unity?

No, actually I created a module in FGC. Then I opened the module in FGU in a new unused campaign without any extensions or other modules (only original 5E ruleset). Then I browsed to the asset folder and imported the image into the campaign by dragging it into the maps folder. Next step was unlocking it and doing all the LOS work. Then save and close FGU. Last step is using the tool to extract LOS data from "db.xml". Because above procedure does not create a moduledb folder. I have put the LOS xml into the unzipped module.

That is why I believe I should work directly in the module after opening it in FGU instead of importing a picture into the campaign. I will try this out today and report back.

Waldbaer
January 3rd, 2021, 22:18
I will try this out today and report back.

It did not work - same result. So my question would be: how could I add LOS data to my module? I attached the extracted LOS data to this post.

Thanks!

42512

Kelrugem
January 3rd, 2021, 22:48
Make sure that you did not move any of the image tiles, do not rotate them, nor scale them :) that won't be extracted, such that offsets are possible. So, just create the map entry with an asset, then only add the LoS; some people moved the tile then etc., and got such different LoS things :)

Waldbaer
January 3rd, 2021, 23:01
that'll be it I guess...only thing I did a lot was zooming in and out with mouse wheel. Do you mean this with scaling? I did not rotate or anything like it. But I zoomed like hell ;)
I doubt it can be easily done without it when working with such a 14MB map...it feels to me as if you are right. Would it help if I just change the "offset value" in the code to "0" again or something like that?

I tried it again with importing into the original FGC campaign like you wrote above with again a strange result (s. another attachment). This really looks as if scaling would be the problem (you can see the small map in the background and it really is not small... :)).

42513

Kelrugem
January 3rd, 2021, 23:06
that'll be it I guess...only thing I did a lot was zooming in and out with mouse wheel. Do you mean this with scaling? I did not rotate or anything like it. But I zoomed like hell ;)
I doubt it can be easily done without it when working with such a 14MB map...it feels to me as if you are right. Would it help if I just change the "offset value" in the code to "0" again or something like that?

I tried it again with importing into the original FGC campaign like you wrote above with again a strange result (s. another attachment). This really looks as if scaling would be the problem (you can see the small map in the background and it really is not small... :)).

42513

Just zooming is okay that is not actually changing the image data (that is then just about the "camera"), but changing the size of the layer with mousewheel and Ctrl (? forgot the hotkey; alternatively changing the size in the sidebar) is problematic :) Difficult to say whether it is that, without overseeing your process of making that :D

Jiminimonka
January 3rd, 2021, 23:23
You do have separate Data folders for FGU and FGC?

Waldbaer
January 3rd, 2021, 23:37
Just zooming is okay that is not actually changing the image data (that is then just about the "camera"), but changing the size of the layer with mousewheel and Ctrl (? forgot the hotkey; alternatively changing the size in the sidebar) is problematic :) Difficult to say whether it is that, without overseeing your process of making that :D

ok. understood. I just did a "one liner" to check this out. I only made "one wall" and extracted it. It did not work, same result. I did not change the map or anything. I did not zoom or scale. Fun fact here is that I now almost believe it could be the map itself. I will try a different one just to check if the process at all works...strange thing.

Waldbaer
January 3rd, 2021, 23:37
You do have separate Data folders for FGU and FGC?

yes, certainly I have. They are even on separate hard disks.

Kelrugem
January 3rd, 2021, 23:49
ok. understood. I just did a "one liner" to check this out. I only made "one wall" and extracted it. It did not work, same result. I did not change the map or anything. I did not zoom or scale. Fun fact here is that I now almost believe it could be the map itself. I will try a different one just to check if the process at all works...strange thing.

Hm, it might be worthy then, to upload that raw image file you started with and to write down all steps to reproduce your issue, such that other people can try it out :)

Zacchaeus
January 4th, 2021, 00:24
This is the order of things.
1 Create the module in FGC.
2 Copy the module to FGU modules folder
3 Start a new campaign in FGU
4 Open the module in FGU.
5 Open the images and maps in the campaign.
6 Draw the LOS onto the images from the images and maps list
7 Close FGU
8 Start the LOS extractor and extract the LOS from the moduledb file in Unity campaign and inject into the Classic campaign/images folder
9 Export the campaign from classic
10 Copy the module to Unity, start a new campaign and test.

I think your issue is adding the images to the Unity campaign from the assets.

Waldbaer
January 4th, 2021, 00:30
meanwhile I tried two further different maps and all reproduced the same error...really strange. I will follow all steps exactly as you posted them and then upload all you need to verify what I did. Hope it's just me :) But not before tomorrow....have a gn8 :)

Waldbaer
January 4th, 2021, 00:40
This is the order of things.
1 Create the module in FGC.


One question on this before I call it a good night: I have several modules where I would like to add LOS. Instead of creating a new one I could also just put this module into the FGU folder, right? Then I cannot export with FGC again but I can follow the dev guide to unzip the module and let the LOS program paste the LOS data into the unzipped module before zipping it again. Correct?

Thanks and have a good night yourself!

Zacchaeus
January 4th, 2021, 09:33
Yes, the first step is to create the module in FGC. If you've already completed this step then you don't need to do it again. You can then move on to step 2. If you didn't create the module in the first place then yes you can extract the LoS into the unzipped FG module (assuming you have direct access to the module and can unzip it).

Waldbaer
January 4th, 2021, 10:42
Yes, the first step is to create the module in FGC. If you've already completed this step then you don't need to do it again. You can then move on to step 2. If you didn't create the module in the first place then yes you can extract the LoS into the unzipped FG module (assuming you have direct access to the module and can unzip it).

Perfect, thank you. I wonder if the problems I have have something to do with the fact that I always tried self made modules until today. Today, as soon as I find the time, I will follow your above mentioned steps precisely and will do screen shots to document. I try this with one of my own modules and also with a buyed one. Let us see what comes out.

Thank you for all of your help and fast replies so far :)

Waldbaer
January 4th, 2021, 14:06
Dear All,

please do me the favor and check my screenshots. I made a detailed step by step guide and I wonder where I messed up. Because the result is again crap...
Screenshots have the names of the steps.

Thank you all already in advance!

4253742538425394254042541

Waldbaer
January 4th, 2021, 14:07
4254242543425444254542546

Waldbaer
January 4th, 2021, 14:08
placeholder

Waldbaer
January 4th, 2021, 14:14
42554425554255642557

Waldbaer
January 4th, 2021, 14:15
Thats it! sorry for massive picture spam...but seems to be the only way to keep it clean. Let me know if something is amiss

Zacchaeus
January 4th, 2021, 14:39
If I am seeing things correctly you are injecting the LoS data into a file with a different name from the original module that you are using to draw the LoS on. You injected into a module with _LOS appended to it. Also you don't seem to have actually unzipped the module in the first place (from what I can tell) it seems like you have added it into the zipped folder. And the map name has an exclamation point on it which might also be a problem. And I don't recognise what zipping tool you are using which could be another issue.

Waldbaer
January 4th, 2021, 17:19
Hi Zacchaeus, thank you for the reply


If I am seeing things correctly you are injecting the LoS data into a file with a different name from the original module that you are using to draw the LoS on. You injected into a module with _LOS appended to it.

That is right - I indeed changed the name of the module file only to make it more visible that this is the module with LOS data included. Do you think that only the different file name can be the reason for this?


Also you don't seem to have actually unzipped the module in the first place (from what I can tell) it seems like you have added it into the zipped folder.

I did - I used 7Zip and unzipped the mod to a folder. Then I included the LOS xml file. Then I went into the unzipped folder and zipped the content with 7zip again. I replaced the .zip ending of the file with .mod and copied it into the unity module folder.


And the map name has an exclamation point on it which might also be a problem.

mmmh...I had easy names in my past modules but yes that could have interfered.


And I don't recognise what zipping tool you are using which could be another issue.

7Zip

Waldbaer
January 4th, 2021, 17:28
That is right - I indeed changed the name of the module file only to make it more visible that this is the module with LOS data included. Do you think that only the different file name can be the reason for this?

I tried it without name change of the file but the result is still the same...

Zacchaeus
January 4th, 2021, 17:35
Can you post the module somewhere so I can test.

Waldbaer
January 4th, 2021, 17:53
yes. Is it OK to post it openly or can I send it over to you somehow?
btw: I finally was successful within my Brittle Bone Tower module. I used a different image and did it almost similar with one difference: I used the export function of the FGC instead of zipping and unzipping myself. Then it worked. I will test this further because I want the real images to work, too.

42564

Zacchaeus
January 4th, 2021, 18:09
You can DM me a link if need be. Obviously don't post here if the module contains copyright material.

Waldbaer
January 4th, 2021, 18:37
You can DM me a link if need be. Obviously don't post here if the module contains copyright material.

PM sent

Waldbaer
January 4th, 2021, 18:38
I almost made it by manually editing the xml file of the mod...but still a bit off everything :) I have to make a break now - makes me crazy!

42567

Zacchaeus
January 4th, 2021, 19:23
Well, I can't reproduce your issue.

I downloaded your module and stuck it into the FGU modules folder and also copied it into another folder and in the latter I changed the .mod to .zip and unzipped it using 7zip. I then started up Unity with a new campaign, opened your module and drew some Los on the map. I then used the tool to extract the file in the moduledb folder and injected it into the unzipped file. I then selected the contents of the module and zipped that back up. Changed the .zip to .mod and put it into the Unity modules folder (overwriting the original). I started up a new campaign and opened the module and the map and the LoS is there as expected.

One thing I didn't think about was whether you have the most up to date version of the tool; make sure you download again just in case (it did change but that would have been a few months ago). I also noted that the map is colossal weighing in at 14MB with a resolution of 4000x5000? It's also a .png file - mas are usually .jpg files and very much smaller. I don't think this has any bearing upon the problem but just be aware that sharing something that size all at once to a group of players could take a very long time. (all of your images are .png files in fact and this means that although your module has barely nothing in it it's coming in at 38Mb - even the DM map is nearly 9Mb)

I've sent you a link to my file via DM.

Waldbaer
January 4th, 2021, 19:38
Thank you so much Zacchaeus. I'll try it again and will also download your version to test it out today. I downloaded the LOS tool last week at this LINK (https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/996645681/Developer+Guide+-+Extracting+LOS+Data+for+Modules). Should be the most actual version I believe.

Waldbaer
January 4th, 2021, 19:45
I really do not get it - your LOS works perfectly fine for me...*grumble* I cannot see any differences within the xml file. It seems I am just to dumb or whatever.... :)

42575

Zacchaeus
January 4th, 2021, 19:49
I think you are doing something just slightly wrong with the zipping or extracting - I don't know.

Waldbaer
January 4th, 2021, 20:11
yes, that might be. I'll try again and report back.

LordEntrails
January 4th, 2021, 20:24
Make sure your zipping tool doesn't have any advanced options and that you are using zip and not another format.

Waldbaer
January 4th, 2021, 20:39
Make sure your zipping tool doesn't have any advanced options and that you are using zip and not another format.

I used the working module of Zacchaeus unzipped it and then zipped it again using 7zip. then I did a new campaign and opened it in FGU. It worked perfectly.
I compared the definitions.xml, the LOS xml and also tried to find errors in the db.xml of both modules - the working one and mine. I did not find any differences that could explain what happens here.

To me that means it can only be the LOS tool maybe? Could you post me a link again and I reinstall? Then I will check again.

Zacchaeus
January 4th, 2021, 20:46
Here you are https://fantasygroundsunity.atlassian.net/wiki/spaces/FGU/pages/260440084/Developer+Guide+-+Extracting+LOS+Data+for+Modules

Waldbaer
January 4th, 2021, 21:30
Here you are https://fantasygroundsunity.atlassian.net/wiki/spaces/FGU/pages/260440084/Developer+Guide+-+Extracting+LOS+Data+for+Modules

reinstalled, made a restart and even tried it on a different module, no change. Maybe I should reinstall FGU...last thing I have in my mind now. Really strange.

Waldbaer
January 4th, 2021, 23:57
Well, I can't reproduce your issue.

I downloaded your module and stuck it into the FGU modules folder and also copied it into another folder and in the latter I changed the .mod to .zip and unzipped it using 7zip. I then started up Unity with a new campaign, opened your module and drew some Los on the map. I then used the tool to extract the file in the moduledb folder and injected it into the unzipped file. I then selected the contents of the module and zipped that back up. Changed the .zip to .mod and put it into the Unity modules folder (overwriting the original). I started up a new campaign and opened the module and the map and the LoS is there as expected.

I reinstalled all of FGU. No change - still the map is far away and LOS is crashed every time I try. I did it exactly as you wrote above - but I think I would like to ask you for more detail. How exactly did you put the LOS on the map. I assume the following steps: you loaded the module, you opened images & maps, you unlocked the map. you made a grid? (I think you did not because the map has already one?) you took the wall/line mode and painted some LOS on the map. you locked and then closed the map again? you saved the campaign by typing /save into chat? you closed FGU through the right mouse button menu?

Thanks...I do not know what I could do next to be honest. Seems to be a mystery to me...your module works with the same basis I use and mine does not. I really have no clue at the moment.

It might be the zipper - but that is not really my first guess because I reinstalled 7zip and tried it with your module. It worked fine...

Best regards and have a gn8,
clueless Waldbaer

Kelrugem
January 5th, 2021, 00:16
Maybe try really just to use windows zipping next time :) I know, you tried that with Zacchaeus's finished module, but that was already finished, so, really try that maybe :) Just to get rid of that possible problem :D

Zacchaeus
January 5th, 2021, 00:19
I loaded the module, loaded the map, unlocked it and drew the LOS. I did’t add a grid. Then as you say saved closed FGU and extracted the LOS using the tool into the copied unzipped module in my working folder. Rezipped by selecting the content, right clicking and selecting 7zip and add to module name. Renamed the .zip to .mod.

Waldbaer
January 5th, 2021, 00:59
Maybe try really just to use windows zipping next time :) I know, you tried that with Zacchaeus's finished module, but that was already finished, so, really try that maybe :) Just to get rid of that possible problem :D

tried it, no change - I think I will make a small video or something tomorrow because I almost do not believe myself ;) This is ridiculous...

Waldbaer
January 5th, 2021, 01:00
I loaded the module, loaded the map, unlocked it and drew the LOS. I did’t add a grid. Then as you say saved closed FGU and extracted the LOS using the tool into the copied unzipped module in my working folder. Rezipped by selecting the content, right clicking and selecting 7zip and add to module name. Renamed the .zip to .mod.

then there is no secret that I could have overseen...still a mystery to me. I will do a video although I doubt this gives more results to me. But maybe an idea what i make wrong.

Waldbaer
January 5th, 2021, 01:04
By the way -> I perceived that the numbers in the xml that the LOS program creates are completely different to the numbers that are in the original xml file when I draw the los within the campaign. This said I copied the original ones into the module, rezipped it and opened it in a new campaign. Then the LOS seems to be correct but a bitt off from the original place where it should be. The resolution is ok, but the LOS is in all cases I have seen so far to the lower right of the place where it should be. Again a mystery to me...but this is an almost correct view - much better than before.

Gn8 guys!

Kelrugem
January 5th, 2021, 01:08
Yeah, maybe a video is indeed the best, probably something very subtle going on :D Gute Nacht :D

Waldbaer
January 5th, 2021, 01:14
Yeah, maybe a video is indeed the best, probably something very subtle going on :D Gute Nacht :D

Will do tomorrow - but here nevertheless a screenshot about how it looks when I copy the LOS data manually from the orginal campaign file to the xml in the new created module without using the LOS tool. This is an "almost" - so frustrating... ;) Gute Nacht!

42585

Waldbaer
January 6th, 2021, 00:41
Hi everyone - as promised, here comes my video from "Waldbaer production". It is really just a fast sum up of the situation and I compressed a 500 MB file to 23MB; but should still be viewable. I excuse myself already now for the music in the background - I needed that ;) Any questions, please let me know!

Hope that I made a mistake somewhere because I still do not understand it at all!

LINK (https://drive.google.com/file/d/1Q8uKPrwL5yNnUlqg6ndRpvLBdJyKAvfP/view?usp=sharing)
(will keep it available there for some days)

Zacchaeus
January 6th, 2021, 11:07
I still think it has something to do with the zipping and unzipping - since this is the only difference between what I do and what you are doing in your video.

So, I copy the module to another folder using windows explorer. I then right click on the module and go to rename and change the .mod to .zip. I then right click on the zip file and select Extract All. You seem to be doing this operation inside an application of some sort. Once I inject the xml I then go to the contents of the unzipped folder select everything and right click and select 7zip and then Add to <modulename>.zip. I then change the .zip to .mod and copy that file into the FG modules folder to test. Can you try doing it that way?

EDIT: I just uploaded a video showing the process https://youtu.be/Nb9Fa6ao2ck

Waldbaer
January 6th, 2021, 17:45
I still think it has something to do with the zipping and unzipping - since this is the only difference between what I do and what you are doing in your video.

So, I copy the module to another folder using windows explorer. I then right click on the module and go to rename and change the .mod to .zip. I then right click on the zip file and select Extract All. You seem to be doing this operation inside an application of some sort. Once I inject the xml I then go to the contents of the unzipped folder select everything and right click and select 7zip and then Add to <modulename>.zip. I then change the .zip to .mod and copy that file into the FG modules folder to test. Can you try doing it that way?

EDIT: I just uploaded a video showing the process https://youtu.be/Nb9Fa6ao2ck

Thank you Zacchaeus - here's my video reply. It is not working either and I did it exactly following your method. I doubt this is a zip issue. The only difference now I see is that you first used FGC to export a "new campaign". I have no clue where a difference might be (because you have been successful with my module and you did not export any campaing I believe?!) - but as I have no better idea I'll try this out.

Here's the LINK (https://drive.google.com/file/d/1lFTuu5v7kG9UT-8NrJPsZoj40lVBSww9/view?usp=sharing).

Thanks again and have a nice day!

Zacchaeus
January 6th, 2021, 18:31
Ok, the only difference is that the map is a png file. Try using a .jpg file. The other thing is that when you opened the map after doing the LOS it did appear that the image was there - only very small. Did you zoom in to see if there was LOS on it?

Having said that I was able to do LoS from your module so that's probably not the issue.

Waldbaer
January 6th, 2021, 20:10
Ok, the only difference is that the map is a png file. Try using a .jpg file. The other thing is that when you opened the map after doing the LOS it did appear that the image was there - only very small. Did you zoom in to see if there was LOS on it?

Having said that I was able to do LoS from your module so that's probably not the issue.

OK - I'll try again with jpg. The LOS is there - but it is in a different place than it should be and slightly off the scale. As if the map changed the scale but the LOS not. This is how it looks to me.

Meanwhile I tried to export the LOS file with the FGC campaign - brings me the same not working result...argh. What a damn thing...

Waldbaer
January 6th, 2021, 20:27
Ok, the only difference is that the map is a png file. Try using a .jpg file.

Tried it . it looks like below picture. Again a total mess. I have no further clue at the moment. Really frustrating...

42645


Did you zoom in to see if there was LOS on it?
Yes, s also above picture. LOS is there but out of scale/zoom or whatever...

Waldbaer
January 6th, 2021, 20:30
damn it...I have another idea. Just give me a sec...

Waldbaer
January 6th, 2021, 20:40
damn it...I have another idea. Just give me a sec...

I just remembered that you only made a grid once in FGC and not in FGU in your video. I always did my grid in FGU. But unfortunately this was not the reason for the mess up. Still not working...*grumble*

Gave m this result:

42646

Kelrugem
January 6th, 2021, 21:08
I just remembered that you only made a grid once in FGC and not in FGU in your video. I always did my grid in FGU. But unfortunately this was not the reason for the mess up. Still not working...*grumble*

Gave m this result:

42646

I just skimmed through the videos (I am really not a video guy, too impatient for it :D), but did you show how you create your FGC module? You use the export function or is there somewhere already your zipping involved :)

(Zippings other than the native windows one already messed up extensions for some people etc.; FG can be sensible to that :) )

Sorry, I just skimmed a bit :D

Did you already try to use the LoS tool just with FGU? (one does not need to create a mod first in FGC, you can create stuff also solely for FGU with it) That may narrow down the problem; when it would suddenly work, then it would mean that you do something with the FGC mod which isn't good :) So, don't start with a module now. Just put an image file into your folder, add LoS, extract, and make that to a module

Waldbaer
January 6th, 2021, 21:17
I suspect I come nearer to the solution. The XML occluder code I generate with the FGU tool is not correct. I did the following: I again created a Brittle Bone Tower LOS that did not work. Then I extracted the module and compare your XML LOS data to mine. Besides the numbers the files are completely similar. Then I copied your data into my xml and raised all content of mine. I did not touch anything else from the created Brittle Bone Tower module. I then rezipped it and put it again into the module folder. And BAM there was the LOS you did perfectly fine.

This said - it must be the occluder data and not the process. So only question remaining is why do I get corrupted occluder data and you not. Below are three files.

I also added the file which I found in the moduledb folder where the FGU tool gets the occluder data from for the NOT WORKING WALDBAER Module...maybe someone has still an idea. I have not at the moment.

Waldbaer
January 6th, 2021, 21:23
I just skimmed through the videos (I am really not a video guy, too impatient for it :D), but did you show how you create your FGC module? You use the export function or is there somewhere already your zipping involved :)

Yes . I think that was all fine so far. And that certainly is not a great to listen to video *LOL* ;)



Did you already try to use the LoS tool just with FGU? (one does not need to create a mod first in FGC, you can create stuff also solely for FGU with it) That may narrow down the problem; when it would suddenly work, then it would mean that you do something with the FGC mod which isn't good :) So, don't start with a module now. Just put an image file into your folder, add LoS, extract, and make that to a module

Yes, I did do only with FGU or only with FGC and so on in all possible combinations. With export from FGC and then to FGU. With grid only in FGC and then in FGU. Only FGU without FGC at all. With just an image both in FGC to FGU and FGU only. etc.

I very much believe it must be the xml code I get when the tool extracts it from moduledb. I just do not understand what goes wrong there...

Zacchaeus
January 6th, 2021, 21:23
I really don't know what the problem is. Can I suggest that you try a completely different image. A small .jpg file not a huge .png file. If you made the module in Classic then it may be that classic didn't like the size of that file - it's too big for Classic by a country mile. Again, I'll qualify that by saying I used the module you sent me and it worked. So I'm clutching at straws.

Zacchaeus
January 6th, 2021, 21:24
I just skimmed through the videos

How dare you skim my videos :)

Waldbaer
January 6th, 2021, 21:35
I really don't know what the problem is. Can I suggest that you try a completely different image. A small .jpg file not a huge .png file. If you made the module in Classic then it may be that classic didn't like the size of that file - it's too big for Classic by a country mile. Again, I'll qualify that by saying I used the module you sent me and it worked. So I'm clutching at straws.

No problem - I did try this already. No different result. I appreciate very much all of your support. Actually who can tell of himself that you made a video because of him *lol* :)

Kelrugem
January 6th, 2021, 21:48
how dare you skim my videos :)

:p ;)

Waldbaer
January 6th, 2021, 22:45
I FOUND IT! Damn it - that is so frustrating but know I have it. It is indeed the LOS tool or whatever is impacting it. At the end the occluder points are not correct. The tool uses a certain factor it seems for the occluder data and in my case it applies a factor ten where it does not need to. I'll show in a video again for who might be interested into it.

That means I now can solve it manually - but the tool does not work for me. Maybe I have the wrong version or an issue with .NET framework?

S. attached screenshot - the left side is the original and the right side the value the LOS tool creates. It is changing the values unexpectedly. If I use the original values from the left side and paste them into the XML of the new module and zip it. All works fine...I have no idea where this is coming from!

Picture from Notepad: 42653

And one more difference I noticed: when I use the fg LOS tool on the db.xml it does not correct X,Y offset. If I use it on the moduledb file then it corrects this offset. My manual method above only works with the db.xml file when there is no correction applied...

So, remaining question would be: any other version of FGU LOS Tool useful or do I have to check on Windows supportive software or whatever?

Zacchaeus
January 6th, 2021, 23:35
I think Doug will need to have a look at what is happening. I’ll alert him tho this thread.

Waldbaer
January 6th, 2021, 23:54
I think Doug will need to have a look at what is happening. I’ll alert him tho this thread.

Thank you Zacchaeus - again appreciated. I owe you a German beer ;) As long as we do not meet I drink one more but only for you ;)

. * .. . * *
* * @()Ooc()* o .
(Q@*0CG*O() ___
|\_________/|/ _ \
| | | | | / | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | \_| |
| | | | |\___/
|\_|__|__|_/|
\_________/

ddavison
January 7th, 2021, 01:30
There are multiple options in the extract tool. One of the options divides by 10. You should not use that option. It was only for very early LOS data that did not use decimal points already. As long as you are on the latest version of FGU and the latest version of the extract tool, you should use the newer method.

I’m away from my PC at the moment, but double check which button you are using and read the labels for all the buttons and checkboxes in the extract tool.

Waldbaer
January 7th, 2021, 14:24
There are multiple options in the extract tool. One of the options divides by 10. You should not use that option. It was only for very early LOS data that did not use decimal points already. As long as you are on the latest version of FGU and the latest version of the extract tool, you should use the newer method.

I’m away from my PC at the moment, but double check which button you are using and read the labels for all the buttons and checkboxes in the extract tool.

Where can I set anyhing in that tool? Maybe my version is wrong? I am fully updated with FGU, FGC and anything else. I use the recommended tool from this link here: https://www.fantasygrounds.com/filelibrary/FGLOSTool_Installer.zip

The factor 10 issue seems exactly to be my thing! But how could I turn it off? I do not see any settings at all in the tool. S. below screenshot of the tool window.

Thanks Doug and best regards,
Waldbaer

42670

Zacchaeus
January 7th, 2021, 14:27
It is the checkbox (which you have unchecked) 'Adjust for old format'.

ddavison
January 7th, 2021, 14:30
Correct. Leave that box unchecked and it should not divide by 10.

Waldbaer
January 7th, 2021, 15:37
Correct. Leave that box unchecked and it should not divide by 10.

Ok...I have never had this checked...

Waldbaer
January 7th, 2021, 15:42
Ok...I have never had this checked...

that is soo strange - I know checked it and it worked immediately...

EDIT: no, does not...just thought it would...here is the screenshot when I have it checked. So unchecking and checking it seems to be a problem.

42671

Waldbaer
January 7th, 2021, 15:49
Here are the files for your reference in the attachment.
If it is NOT checked, he multiplies by 10.
If it is checked I have no clue what he does...

Zacchaeus
January 7th, 2021, 15:53
Can you screen shot the folder with the FG LOS tool in it.

ddavison
January 7th, 2021, 16:01
Here are the files for your reference in the attachment.
If it is NOT checked, he multiplies by 10.
If it is checked I have no clue what he does...

Can you include the moduledb XML file after you added the LOS from your video in the test campaign and also the map image? You can email it to me if you'd prefer: [email protected].

Waldbaer
January 7th, 2021, 16:34
Can you screen shot the folder with the FG LOS tool in it.

There you go - I haven't changed it. This is the folder that the tool recommended.

42679

Waldbaer
January 7th, 2021, 16:55
Can you include the moduledb XML file after you added the LOS from your video in the test campaign and also the map image? You can email it to me if you'd prefer: [email protected].

email is sent

Zacchaeus
January 7th, 2021, 17:39
There you go - I haven't changed it. This is the folder that the tool recommended.

42679

Yeah, that looks good. I was just wondering if there were any differences between yours and mine that would point to a version difference maybe.

Waldbaer
January 7th, 2021, 17:42
Yeah, that looks good. I was just wondering if there were any differences between yours and mine that would point to a version difference maybe.
Appreciated :) - let us see if Doug can figure it out. I can now help myself manually by just editing the xml myself. But might be of help for others. If I am the only one with this problem I am ok to keep it as it is...

Garou
January 19th, 2021, 09:57
Hello Waldbaer and all others

Just like you, I have the problem that the LoS data cannot be extracted. I have had fantastic help from Zacchaeus via Discord, but like Thomas Edison, we have yet to see the light; we are still within 10,000 tries of finding out how it doesn't work.

Received a reply from support this morning, but unfortunately it didn't solve the problem. However, I have replied, referenced this thread and sent a couple of screenshots - perhaps this will help resolve the issue.

Zacchaeus
January 19th, 2021, 10:12
This issue has to be related to something on the user's machine I think. Garou sent me his module file and the moduledb file and I was able to extract the data into the module just fine and the LoS shows up correctly in a new test campaign after extraction.

We have tried many different scenarios but just can't get it to work correctly for Garou.

Kelrugem
January 19th, 2021, 10:16
Funnily, Zacchaeus, I wanted to suggest the same. Because I just had the funny observation, that every time (I remember) someone reports that error then it is seemingly a report from aGerman :D Might this have to do anything with that we Germans switch the meaning of commas and dots when it is about digits? (because of the previous factor 10 problem) Something like that, related to the UI etc.; but I am really shooting in the dark now :D

When I find time, then I finally need to test this tool, too; if it is indeed related to German UIs, then I should get the same problem

Zacchaeus
January 19th, 2021, 10:26
Funnily, Zacchaeus, I wanted to suggest the same. Because I just had the funny observation, that every time (I remember) someone reports that error then it is seemingly a German :D Might this have to do anything with that we Germans switch the meaning of commas and dots when it is about digits? (because of the previous factor 10 problem) Something like that, related to the UI etc.; but I am really shooting in the dark now :D

When I find time, then I finally need to test this tool, too; if it is indeed related to German UIs, then I should get the same problem

Well that's certainly possible. Garou and I shared screens and worked through the extraction process and he's doing the same as what I'd do. He did have different options for extracting zip files than I did on the right click menu and we couldn't figure out why that was - but I can't see that being an issue. Once I had extracted the LoS and sent him back the module the LoS worked for him. So it is down to the extraction process somewhere. But if you do some testing hit me up on Discord if you find anything relevant.

Garou
January 19th, 2021, 10:36
Keaton and I have thought about that too. Still, two facts confuse me. One and the same file can be extracted and inserted sensibly by Zacchaeus in Scotland, whereas Keaton from Denver, with whom I worked on the module for Gooey Cube, also has problems and sees the same chaotic representations of the LoS.

The module that Zacchaeus had then created and uploaded, I could open regularly, but unfortunately I could not recognise any LoS data.Therefore, it is reasonable to assume that it is a "German" problem.

On the other hand, Keaton could not create the module with LoS - unlike Zacchaeus. In both cases the data sets were identical... All very confusing...

Kelrugem
January 19th, 2021, 11:01
Oki, I tested now

It has to do with the language settings of the UI. I tested with my German settings and I had precisely the same errors. Then I changed the language of Windows in the settings, so, everything is in English now, which is also why this is probably the first post here from me without smileys, because I have no idea where those bloody colons are on an English keyboard!

However, with the English settings it works perfectly for me now.

Garou, you could ask Keaton which language they use for their OS, might not just be related to German. The language seems to mess something up in the extraction process

Kelrugem
January 19th, 2021, 12:00
Hah, I got even more information, my previous guess why the language settings may influence this was true!

It is indeed due to the meaning of the dots and commas with respect to digits! :D Go to Windows' Region settings, click on advanced settings, and then again advanced settings, then you can change the decimal symbol and the digit grouping symbol. When the decimal symbol is a comma and the digit grouping symbol a dot (as in German, the opposite meaning than the English definition), then I get erronous extracts, even with the English UI! :D May also just result into that when just changing one of both :)

Detective Kelrugem to your service :D

Zacchaeus
January 19th, 2021, 16:28
Awesome detective work Kelrugem; that's brilliant.

Garou
January 19th, 2021, 16:56
YOU ARE JUST INCREDIBLE!!! I will test it by tomorrow, still busy.

Kelrugem
January 20th, 2021, 04:38
YOU ARE JUST INCREDIBLE!!! I will test it by tomorrow, still busy.

I hope switching the definitions of comma and dot will help you :D (not that there is something else influencing that, which also got changed when I switched to the English UI)

But I hope that this will help the devs to update the tool to cater for that :)

Garou
January 20th, 2021, 08:18
It's such a relief now that it works! Just changed the decimal number separation, then added the LoS to the module as it was intended and inserted it into FGU, created a new campaign and tested the module. WOW! It works! Unbelievable but true! What such a small character can do! If you could see all the new grey hairs! Anyway... To be on the safe side, I then set my computer to default and restarted it, then started a new campaign in FGU and loaded the updated module - it works without a hitch! Thanks again to Zacchaeus, Kelrugem, Waldbaer and Keaton. Without you I would still be in the dark!

Kelrugem
January 20th, 2021, 09:26
Cool :) Then we have found the culprit and a workaround :) That has certainly only an influence in the extraction tool itself; once the module works it will always work because it cannot be a problem with the xml reading of FG itself, otherwise there should be a lot more problems :D

ddavison
January 20th, 2021, 14:44
Hah, I got even more information, my previous guess why the language settings may influence this was true!

It is indeed due to the meaning of the dots and commas with respect to digits! :D Go to Windows' Region settings, click on advanced settings, and then again advanced settings, then you can change the decimal symbol and the digit grouping symbol. When the decimal symbol is a comma and the digit grouping symbol a dot (as in German, the opposite meaning than the English definition), then I get erronous extracts, even with the English UI! :D May also just result into that when just changing one of both :)

Detective Kelrugem to your service :D

Great detective work Kelrugem. I spent a while trying to recreate it and completely missed that as a potential cause. I will have to check and see if there is a way to account for that somehow in the process.

Kelrugem
January 20th, 2021, 15:49
Great detective work Kelrugem. I spent a while trying to recreate it and completely missed that as a potential cause. I will have to check and see if there is a way to account for that somehow in the process.

:)

Would certainly be cool when it can be somehow fixed :)

Waldbaer
January 22nd, 2021, 17:04
Detective Kelrugem to your service :D

I have to bow before you Kelrugem - that is really great work. I lost like 4 hours of my life with this terrible problem and because of all the trees I could not see the forest ;) Thanks a lot! Hope Doug could update the tool because I could never survive changing dots and commas on my keyboard forever ;)

*bow*

Waldbaer

Waldbaer
January 22nd, 2021, 17:07
It's such a relief now that it works! Just changed the decimal number separation, then added the LoS to the module as it was intended and inserted it into FGU, created a new campaign and tested the module. WOW! It works! Unbelievable but true! What such a small character can do! If you could see all the new grey hairs! Anyway... To be on the safe side, I then set my computer to default and restarted it, then started a new campaign in FGU and loaded the updated module - it works without a hitch! Thanks again to Zacchaeus, Kelrugem, Waldbaer and Keaton. Without you I would still be in the dark!

Nice city you are living in by the way - it might be that we are neighbours because it's almost mine, too :)