I use to “box” type for textures. But recently this is happening. I don’t know why. I even reinstalled Windows but “box” type still doesn’t work well !!
Hi @arch.salimi
If you can upload your model and texture it’ll be easier for people to diagnose.
In box mapping mode did you try turning on the mapping widget and orienting and scaling it to your object? Looks like your object is skewed to the mapping widget.
RM
Your texture Position datum is seemingly 178,000 units from origin in X, and even larger in Y. Is this also where the object is located?
I guess this is causing serious numerical errors?
Hi @arch.salimi
This looks like a rendered display bug try setting your viewport to raytraced that cured it for me.
I think this is a bug or shortcoming in rendered mode, raytraced is fine and so are renderings.
This looks like it crept in with the last update I don’t recall having this problem before. I work on large architectural projects for vfx.
I attached a file which shows the problem, I tried to emulate your settings. You might want to provide your model as well and machine specs. I’m on V7 but it looks similar.
machineSpecs.txt (3.0 KB)
texture-far-from-originProb.3dm (1.0 MB)
RM
Hi,
Your file seems a bit messed up, your mapping widgets are far from the objects. Your object is tiny in millimeters so box mapping won’t work on it. The object in the file is too small for the repeats. I was able to get one of your objects to work I had to scale it larger than align the mapping widget to the orientation. Lastly there were no textures in your file you must have forgot to check the save textures box when you uploaded so I tried with the standard brick material from rhino library.
I think in last file I uploaded there might be a problem since I detected a bug but in current file you provided it seems something is up with your scaling and mapping widget. Why are you working so small (your object is 1/2 a millimeter) and then placing something microscopic so far from the origin? If you’re working on architecture I’d work in meters not millimeters.
I was able to get your one object working by scaling it larger and aligning the mapping widget to it. It is far from the origin and is still working.
RM
far origin-2.3dm (2.2 MB)
Hello @3dsynergy
Thank you for your good explanation.
I also changed the dimensions and scale, but it didn’t work.
And as for why I work in millimeters, I should say that first the mapping&surveying of the area was taken with millimeter precision and I need to work on that file with the same precision.
far origin_3.3dm (1.0 MB)
Hi @arch.salimi
Thanks for the textures check, I don’t have V8 so I think the file translator I use to translate V7 maybe nixed your image files.
Same problem as before your mapping widgets are out in space somewhere far from the object. Also it’s the same bug or floating point math problem so even though I can get it to work in Raytraced mode it doesn’t work in rendered mode.
There are two ways to set box mapping one is the auto option and the other is the user option. Use the user option and follow the command prompt and make sure you orient the widget to your model. Notice how I did in the image below. But I don’t think all of this will be of much help. You’re almost 400000 meters away from the origin with these objects.
Best to contact Tech support and upload your “complete file” for Rhino tech to look at, it’s confidential and hopefully they might have an answer.
Sorry I can’t be of more help.
RM
far origin_3a.3dm (808.3 KB)
Hello again.
Sorry for the late reply.
I tried both mapping options but the result was the same.
Ok. so i should contact Rhino tech
Thank you very much for your time too
Hi @arch.salimi ,
I’ve filed this issue for the developers, thanks for the report. I think the only solutions presently are to use Surface mapping and then adjust the UV meshes in the UVeditor or move the model closer to the world origin of 0,0,0.
