Search this Topic:
Feb 3 11 5:47 PM
Feb 3 11 6:57 PM
Feb 3 11 7:22 PM
Feb 4 11 4:12 AM
Feb 4 11 4:50 AM
Feb 4 11 5:43 AM
Feb 4 11 6:13 AM
Feb 4 11 8:19 AM
Feb 4 11 8:39 AM
Feb 4 11 8:52 AM
Feb 4 11 9:16 AM
Feb 4 11 12:58 PM
first of all: great work! Especially as this was your first Erlang experiment?
<<Done, but i would like to use the file extensions supported by wings (from wpa:image_formats()) but i got error when concatenating the final string in this macro:?__(3,"File browse for "++Fs0++" then provide options")where Fs0 = "bmp,jpg,png,tga,tif">>
I'm pretty sure, that string concatenation with ++ inside the ?__() translation macro is not allowed (makes no sense), because these strings are extracted into the *.lang files. Also string translations of e.g. ?__(3,"File browse for ")++Fs0++?__(4," then provide options") are very hard to translate because of different order for subject/object in different languages. The right way to go here is along this line: io_lib:format(?__(3,"File browse for ~s then provide options"),[Fs0]), that is, use placeholders in the string to translate, which will be filled in at runtime. That way translators can put the placeholder anywhere it makes sense in their language (and even change the ~s to ~ts for unicode strings, e.g. in korean).
edit: corrected io:format to io_lib:format (io: is for printing to stdout/console, io_lib: returns a character list)
Feb 4 11 1:27 PM
Feb 4 11 3:54 PM
Feb 4 11 6:31 PM
Feb 4 11 7:37 PM
now I started to check your nice new plugin, and it is really useful. Besides, thanks for your video, explaining the UV mapping work flow (for the -90┬░ rotation also see below).
Something seems to be wrong/unexpected with the aspect ratio in your dialog. My height map image is 133x100 (the texture [photographed by my son] 1000x750). Your dialog shows reasonable suggestions: 8.0 x 6.015038 (ratio 1.33 as for the height map image), but the 'terrain' generated had dimensions 7.93985 (~8.0, that's ok) x 4.477359 (~4.48 instead of ~6.02, wrong) and thus the circle shaped object was distorted to elliptical. Then I tried to just swap the width/depth values: the circle was distorted again elliptically in the other dimension, but the ground plane was now quadratic. My workaround was to disable "Aspect ratio" and enter 8.0 into both fields ... then I got the correct result. You'll know what's wrong.
Besides, "Deep" should read "Depth" in English. And may be better to rename the dialog parameters to "Length (X)", "Width (Z)" and "Height (Y)" ...
... which leads to the next suggestion: instead of having to rotate the UV map by -90┬░, what if you do that rotation by default, when generating the terrain? I tried and rotated the terrain mesh by -90┬░ before attempting to UV map the top/terrain faces and got good results without rotation in AutoUV.
And I second ggaliens suggestion to not generate all these vertices on the -Y base face. Look at the grid primitive: it has a clean rectangular base face (4 vertices) and the side faces are also clean as much as possible (just having many vertices/edges on the "upper" side, where the grid lives, but just one face). Your plugin generates "sort of a grid", doesn't it?
I think, the <<the mesh has moved when i used smooth preview>> would no longer be there, because of the hard edges you automagically generate for the ground/side faces.
Thanks for your nice new plugin, Georg
Feb 5 11 7:46 AM
Feb 5 11 9:40 AM
Feb 5 11 9:43 AM
Feb 6 11 3:09 PM
© 2017 Yuku. All rights reserved.