Tutorial: placing a tile on a planetary surface.

[selden]

jogad,

Exactly what editor were you using?

There have been similar issues when people use "word processors" instead of "text editors" to edit Lua files. Word processors assume you are working on a document for publication. They automatically convert two hyphens (used in Lua to specify a one-line comment) into an em-dash (double-wide dash), which Lua doesn't recognize.

[t00fri]

jogad,

Exactly what editor were you using?

There have been similar issues when people use "word processors" instead of "text editors" to edit Lua files. Word processors assume you are working on a document for publication. They automatically convert two hyphens (used in Lua to specify a one-line comment) into an em-dash (double-wide dash), which Lua doesn't recognize.

I was precisely thinking of such cases, too. Lua and Maple, for example use { } parantheses a lot. I would never use anything that changes characters without asking me...

Fridger

[jogad]

I usually use Notetab Pro or Notepad2 if I must have characters with accents and I have no problem with that.

The problem for me is that when I want to post a message in English I use Microsoft Word which corrects a little part of my spelling and grammar mistakes in this language.
In this case the original curve brackets were in the text but were converted when I pasted in the input box of the forum. This is strange and maybe I did something wrong.

But thanks to you this error is fixed in the tuto.
I am interested to know if the two points that you emphasized (64k TileSize and lack of intermediate levels) may cause troubles on some systems?

[t00fri]

I am interested to know if the two points that you emphasized (64k TileSize and lack of intermediate levels) may cause troubles on some systems?

I bet 64k tile size would indeed cause problems. Fortunately you had only written 64 (pixels). While we have agreed since a long time that making the tile size somewhat smaller than the actual size retains better focus in the interpolation between the various levels, I would be surprised if making them smaller by a factor of 32, doesn't have some negative impact...If it hasn't, then there would be no good reason why one should specify this parameter at all...

Fridger

[jogad]

Sorry, I did not understand the 64 pixels. For me, the statement TileSize 64 means 64k. I am wrong?

I am well aware that this is a particular case. Indeed there are only 3 tiles in the texture virtual instead of several hundreds or thousands.
And there is no interpolation between the levels because we go directly from level 0 to level 9 or 10.

The aim was that the texture appears from more away to spot it more easily.
With the declaration TileSize 64, it appears on my screen at a distance of 24km while with a statement TileSize 2048, it appears only at about 700m and it is not possible to see it entirely.
On my system 64 is the smallest possible value that works and that is why I have chosen it.
This value works well only in this particular case with a single tile at the highest level and 2 tiles at level 0.

This is precisely why the value of this parameter can be specified depending on conditions. Otherwise I agree it would be needless to precise it.

What I do not know is if this value is possible whatever the system. If this is not the case, I'll change the tuto.

[t00fri]

Sorry, I did not understand the 64 pixels. For me, the statement TileSize 64 means 64k. I am wrong?

TileSize is in pixels!

Fridger

[jogad]

TileSize is in pixels!

Yes of course! it's evident!
Thank you Fridger.

But the question remains the same.

[PlutonianEmpire]

Sorry for bumping.

Ok, I did a comparison between the OP's Excel VT calculator and Fridger's Excel VT calculator, and noticed that the +/- designations in the "error on X" in the OP's calculator appears to be inverted, where a negative number should really be a positive number, and vice versa.

For example, I have a tile size of 4096 pixels, and Fridger's calculator tells me to put my texture at X: 2099, Y: 2538, whereas the OP's calculator gives me a X error of -51 and a Y error of -490, which means the OP's calculator is telling me to move my texture to the left instead of the right. The Y error of -490, of course, tells me to move my texture down(/south), and is thus accurate.