Hello,

I am in process of updating the engine, and I have a problem with the node materials.
Previously, I used every slot, searching at the object batches, changing the textures as needed.
Now, on exporting, the textures are not named as before (there's no texture.name, but at least I have batch.bpy_tex_names for that), but it is not showing all my texture slots, only 4 of 7, and kind of random between different exports (it doesn't always show the same ones).
I am trying to understand if it is an export problem, something broken with my nodes or if something has changed since many versions ago.
Could you please provide some guidance on what to look for?

Thanks Pavel, I will try those out.
I cannot really share the .blend, as it is considered an enterprise secret, sorry.
That's why I made several screenshots.
Anyway, at least now I know where to start to look at.
I will notify you with the results, so maybe it would help someone else .

Hello everyone!

Raúl Loza from Alugroup here.
I don't really know if this is really a bug, or something that has changed without me noticing.
I have been following your great work in updates, and finally got some time to go ahead and update the engine myself.
I have tested both 16.08 and 16.09 versions, and everything works great but for a couple of changes I can see on materials.
I use Node Materials, and I can see new parameters in those, but probably you will know better what happens here.
I attach some screenshots so you can view the differences between "orig" and "new".
The main problem comes with cubemaps, that appear somehow rotated, meaning the bright spot is still there but in another position (screenshots 1 to 4).
Furthermore, the falloff effect I use for suede material seems stronger than usual (screenshots orig_suede vs new_suede).
I wonder if you know the parameters or anything new than can make these differences from 16.01, so it will be easier to update the Node Material (quite big monster right now).

Thank you very much!

Well, I suppose it should work.
I will try and notify you later.

Thanks!

Hello Konstantin,

Thank you for your response.
That's exactly what I thought, that the camera fits height.
What I'm trying to figure out is some way to render the shoe fitting the screen's width, but when rotating it pointing downwards it gets cut (like when zooming in), even though I still have extra screen height.

I can imagine some way to tell the camera viewport to be some rectangle taller than wider, taking profit of the screen size in portrait mode.
Of course this would require some kind of calculus to match the camera viewport to the current canvas dimensions .
For instance, an iPhone 6 in portrait mode could have, in theory, a canvas 375px width, ~600px height, but for our current 16by9 canvas it adjusts to 375px width, 0.5625*375 ~= 210px height.
But if I make the canvas full width and full height, the shoe renders outside the screen's width, instead of fitting inside, which is not desirable.
And if I maintain the 16by9 resolution, it renders properly from side to side, but it gets cut when pointing downwards.

Probably there is no easy solution to this, but worth asking you guys that have more experience in these matters.

Thanks again!

Hello everyone!

In our project we have made the canvas responsive and 16by9, but now we are considering to change to container fit, specially for portrait mobile.
I mean, for instance, instead of being 16:9 the canvas will look something crazy like 5:10.
But trying to do this makes the camera fit for height, and as it is wider than the allowed with, the 3D object gets cut.
We are thinking in making the camera fit the width, but also needing the extra taller canvas, so when the object rotates it doesn't get cut at the bottom or top.
Attached a couple of screenshots of what I'm trying to say.
Ideally the object looks "tiny" as in "cut.jpg" but can render at bottom as in "extrawidth.jpg".
Is there any easy way to make this happen??

Thanks in advance!

– Raul, Made in Me developer