Hi, V5
done this a few times by now, yet today import a mesh, apply texture.
click mesh go properties. paint tube icon
colour click and browse to the jpg, select it.
setObjectDisplayMode rendered, and my nice bright correctly exposed looking good in Agisoft , wheel IS NOTABLY DARKER.
all my efforts in raw mode and on site getting perfect exposure and it looks fabulous in Agisoft and this happens in Rhino.
I need it as it should be so as to draw all its details.
I try again in V8 and its as it should be. so why has V5 gome dark on me, others from that day are ok.
But I use V5 for all these, why suddenly darker ?
also its come in as two meshes so two allocations to do, export it again and still two meshes,
metashape 2.2.2 latest version.
Hi
something has gone wrong with Agisoft, I updated to 2.2 a few days ago, as here is proof, open one done a year ago then import the export made yesterday. into same view, ( I never change the lighting anyway, dont know how)
Hi,
well thats the entire evening spent backing up Pc twice as first backup simply vanished.
then install latest drivers’ 23 days old, test a flight sim !
and export again the model then import.
and no difference
I uninstall metashape 2.2 and reboot, install 2.1.1 from april 2024
redo the entire project,
import obj, still I get two meshes and two .jpg same name same size etc.
select mesh and guess at which is which, wrong, try again also wrong,
export again, and import again, same problem, unable to select correct jpg for that part of mesh.
try in rhino v8 and SLOW SLOW SLOW, hear graphics card working hard, interfaces eventually appear. something not right, V5 a lot quicker,
mesh is white,
unlike V5 fast, but able to select setObjectDisplayMode and see correct texture.
as V8 allocates the texture using code in the obj whilst you have to do so yourself in V5.
get both meshes showing as should be, and correct brightness, but V8 acting very slow with them.
and then redo it all again in Agisoft Photoscan, my go to if something is wrong, and export as obj.
This time its ONE MESH.
a few less polys.
BUT IN V5 ITS DARK.
what is going on ?
and in V8 ok. and quicker.
Hi,
unaware of fbx, somehow either the default in Agisoft was obj or I asked and was told use .obj
so looked to see if Agisoft metashape has such and it has.
export as an .fbx
go to RhinoV5 and select .fbx from the list, its a motionbuilder file
import it, and nothing appears, error it says, try again and again error.
so fail trying .fbx
I have never up till now had dark import, and this is probably my 30th or so rhino project using agisoft. so V5 is free of blame it seems.
I also dont know why both metashape 2.2.0 and 2.1.1 puts out a twin mesh and 2 x jpgs exact same name and size but different artworks for this obj.
and Photoscan put out a normal single mesh with single .jpg
I ripped 2.2.0 off PC, as no revert to previous versiion available, Installed 2.1.1 from my stash of progs, and still it makes a twin mesh and twin jpgs, and now they wont map correctly to the model, though in V8 they do.
I then use Photoscan, as metashape often fails me, and I get ONE MESH. and a mappable .jpg but its still dark in V5.
why oh why is this happening ?
first time V5 doing this to me. yet is ok on other Agisoft exports.
and If I can place two side by side, a previous one ok and this one dark, it just defeats me as to why .
Hi,
Ok will do, so where would this be , and what am I looking for, what does it look like in V8, maybe I can then dind same in V5
I have had a quick look in properties under render and appearance and such like but dont see anything, but may have overlooked what I am supposed to be seeing.
Imagine a time when only V5 existed, so nothing to compare it to, and after many normal textures this happens, how can it be that a setting is ok until one day not ? puzzled.
I can’t answer for Steve, but I also export meshes from Metashape by Agisoft to Rhino and I also use OBJ. I started using OBJ in 2012 because it was widely used with a published specification. OBJ is one of the formats recommended by the Library of Congress for archiving scanned data.
My experience with importing textured meshes into different versions of Rhino from V4 through V8 is differences in default lighting have caused textured meshes to appear differently.
Hi David,
r u pro or Std ?
I am metashape standard, bad enough without paying a lot more for pro.
I wonder if pro woild be buggy free,
does metashape send you doolalley at times, ?
why a mesh in two halves yet Photoscan with same images a single mesh as it should be !
align fails and Photoscan all align.
I was glad this wheel all aligned, but then !!!
I am now about to process the many more pics withput ruler, lets see what happens !
and hey presto, the one without rulers, photos taken immediate prior the ruler one, and all is as normal ! in V5 !
just what is it about those with ruler taken after those without, all dealt with in same raw mode. same adjustments,all look same in pshop, and in Agisoft. does my head in 2 days battling.
Agisoft has shown its their prog that had altered things.
firsly getting two meshes which together for the mesh, is called 2 pages, and in the export box there is a 1 or a 2 or more, this was locked to 2, and I never did that as I never ever wanted to dabble there.
unable to alter to 1.
it meant redoing mesh texture making using generic, and not keepuv.
Imported the obj from that and still dark but at least ONE MESH now.
Then it was still dark,
then I discovered that the good ones were vertex colour ON and vertex normals OFF.
but that option was again LOCKED OUT.
and so had to redo mesh vertex colours, method being…
Tools>Models>Colorize Vertices option.
