working on a obj mesh with texture mapped.
Attempt to import into V8, necessary to have the existing 1:1 dims open ok in the V8 1:1 dims template.
it comes in but the raster mapping is not right !
go file open and try again and its ok.
However we need the import method for the dims for all V5 projects, (many)
why has import not honoured the texture mapping ?
There are three meshes in the project, the other two see correct mapping.
the bad one was the one ‘visible’ at time of saving in V5, the other two being turned off.
test turn it off then save as suffix visOff.
open in V8
still bad.
Hi,
I am using the link from a recent thread, that Wim picked up on the upload of another mesh.
I am sending the big project , three meshes, and zipped it all up, and clicking the red button ‘upload now’ nothing happens.
I reckon it uploads before that button does anything.
we could do with a progress bar so we know when clicking the button does actually allow something to happen ! tech@mcneel.com was the email address the link showed.
5 mins later and still that button does nothing.
on the tab upper left is a rotating blue circle, 15 mins later and stil rotating.
what other method is there of uploading this to McNeel as this method seems full of holes.
I will try for pcloud instead as this is prehistoric !
at 1Mb/sec ploud also prehistoric.
1.7Gb file to send.
in this day and age is there not anything better McNeel has ?
not following why test is exporting v5 to an obj ?
the problem is a V5 .3dm file that has functional meshes with mapped textures, loses the texture on one of them when the .3dm is imported into v8, whilst file open keeps the texture.
The key here is if the OBJ file has two Textures named exactly the same. if this is the case, then matching them back up can be impossible. We can look closer.
What is the source of this file? What App created it?
Hi,
I will try that link again, but after 1 hour of occasionally clicking the red send button I still had rotating blue circle on the tab top left.
That pcloud transfer should have got through.
I will try again with the rhino link.
its 1.7Gb and zipped.
each obj is a different name, and the file name is also pasted into the layer its on.
no point in creating another as its this project I need to get into V8 and we need to know why it failed on the one obj, when using import mode.
wish me luck, uploading again.
2hr 26mins online calc says for 1.544mbps and 1.7Gb.
initiated 20.35 appx.
Its a lousy interface no indication its happening, click the bitton, doesnt change colour or anything.
Just starts a bouncing left right grey dot on the tab.
there wont be a problem as such as all have different names and correspond to the names on the layers.
the layer with the problem is
NO RULER V2 OBJ M 2.2.0 TypeC MkIII EK NsideFrontBrakeAssyV3PSCAN allALIGN high2.9Kp6colvert
and the obj is named within it,.OBJ M 2.2.0 TypeC MkIII EK NsideFrontBrakeAssyV3PSCAN allALIGN high2.9Kp6colvert
hope this sends as apart from a grey dot going left to right, no progress bar, etc.
aha upload done it says, so you have it.
Hi,
glad it arrived.
V5 save file as
file ending in template v3 MESSABOUT.3dm
close Rhino5
Open Rhino8 choose new and cannot see file names so choose something.
then go new and this time get big screen file explorer and readable names.
choose Small Objects - Inches Decimal V8 1to1 ready for V5.3dm
go file import and browse to the rhino5 saved above.
after a few secs it arrives, and as I had saved it with the layer No Ruler V2 turned on, showing the trolley,
the first I see is as in image at start of thread ! wrong image mapped.
I turn off that layer and turn on the ruler obj layer and thats ok, then turn on the non ruler above that and thats ok.
save the file suffix intoV8.
then try process this time using file > open method and its all ok, BUT the dims are a mess.
Thats why i used that template and import as the dims are set up as 1:1 matching the styles and model space dims of that V5.
The method to be used for bringing V5 projects into V8 and having dims behave. Subject of another thread let alone months of angst over V5 into V8.
