fyi: I sent it yesterday also to the support to be checked.

thanx

i experience the same problems, when using hit.u1/v1/u2/v2

It seems as if it has problems with rotating (just use a simple model, check the u1 value and one point - remember this point, rotate the model, check u1 and the same point as before ==> wont be the same)

Please check this, u1/v1 is a very important feature for me..

@TechMuc

It's another bug but no moderator moves this post to the bug forum...

I'm basically having similar issues with the UV coordinates. Unfortunately, I can't read german and would like to know if someone here that can read it summarize if the problem can be worked around? We're trying to make a golf game and we need to know what type of material on the terrain the ball hits. We're doing this by looking at the colors in the texture using the UV coordinates. Anyhow, if anyone has any suggestions, that would be superb. Thanks.

This is an old thread, when you look in the bug list you see that this was fixed long ago.

...but it still does not work... *sight*

There was a scaling fix for hit_... in 7.65
So it should work with the next public beta.

Yes, there was a bug when the scale was different to 1, but apart from that I am not aware of any current u/v problem. If I remember right, the level you've uploaded had just the problem that you were hitting not polygons but bounding boxes. When you want UV coordinates, make sure to use polygon mode, otherwise your hit point is not inside the polygon.

If you want, download the latest version, 7.66, here: http://server.conitec.net/down/gstudio_766.exe. If it still does not work with that version, I'll have a look into your code. Please send it to Support then - we'll check what the problem is.

Thanks, we'll check it out.

@jcl: you're right - now it works fine (my fault on testing it)