I guess there are many more out there...
I created a ticket in the FT 5160.
I kindly ask you to vote it in order to let RL hearing us.

Cheers

  Roberto



My PC:
OS: Windows 10 Pro English 64-bit / CPU: Intel i7-9700 3.6GHz / MB: ASUS ROG Strix Z390  RAM: 32GB DDR4 2.6GHz / HD: 2TB+3TB  /  SSD: 2x512GB Samsung 860 EVO + 1x2TB Samsung
VB: Palit GTX2080 TI GamingPro 11GB / AB: embedded in the MB and VB (audio from the MOTU M4 I/F) / DirectX: 12

Hi Roberto, i managed to export nude character with lowest LOD to 3Dxchange and used autoconversion. Working fine in iClone and ended up with 362 triangles :-)
Christer


My computer: Intel i7-7700K 4.2Hhz 64Gb, Windows 10, GeForce GTX 1080 + GeForce GTX 1070, Phillips monitor 40" 4K  3840x2160 + 2x28" 

Hi Gerry,

I see the point.
What was the reason ?
SW programming issue ?
Did RL committed to fix the issue ?

Anyway, the quick&dirty work-around would be to have from RL the 3DX template to re-target the bones in 1-click.

  Roberto



My PC:
OS: Windows 10 Pro English 64-bit / CPU: Intel i7-9700 3.6GHz / MB: ASUS ROG Strix Z390  RAM: 32GB DDR4 2.6GHz / HD: 2TB+3TB  /  SSD: 2x512GB Samsung 860 EVO + 1x2TB Samsung
VB: Palit GTX2080 TI GamingPro 11GB / AB: embedded in the MB and VB (audio from the MOTU M4 I/F) / DirectX: 12

@toystorylab >>> " ... LOD-function in CC3 Pipeline was one of my major reasons (crowds in iClone) to buy it. ... " <<<
Same here ...

--------------------------------------------------------------------------------------------------------------------------------------------------------

Please be patient with me ..... I don't always 'get it' the first time 'round - not even the 2nd time! :(  - yikes! ... 

● MSI GT72VR Laptop, i7 7700HQ 4-Core 3.8 GHz 16GB RAM; Nvidia 1070, 8GB Vram ● iClone-7.93 ● 3DXChange Pipeline 7.81 ● CC-3 Pipeline 3.44 ● Live Face ● HeadShot ● Brekel Pro-Body ● Popcorn FX ● iRAY ● Kinect V2 ● DaVinci Resolve17 ● Mixcraft 8.1

Roberto,
The Beta tests proved that a remeshed iAvatar just doesn't work correctly at the moment and that is why the option has not been included.
The mesh reduction option does work and permits full use of materials and collision shapes while not using too many resources.


Gerry

---

System: Win 10 Pro (21H2), Asus X99-E WS, CPU i7-5930K -3,5 GHz, 32 GB DDR4 2666-16 RAM, NVidia GTX 1080 Ti GPU - 11 GB VRAM(Driver Studio-536.99), Samsung 850 Pro 512 GB SSD, 6 TB HD storage.

Hm, i pre-ordered CC3 + Iray-Plugin but did not install yet, quite busy and want to wait till most issues are polished...
BUT what i read from "RobertoColombo" and "wires" makes me wonder.
LOD-function in CC3 Pipeline was one of my major reasons (crowds in iClone) to buy it.
And the announcement said it would work in iClone!
WHY is there no "send to iClone-button" for remeshed characters?
And how did these characters (from my understanding not only "Reduce Wearables Mesh") shown in Promo-Video end up in iClone?

75% of original size (was 672x19) - Click to enlarge


Toystorylab on Vimeo : 75% of original size (was 672x19) - Click to enlarge    Crassitudes (my "Alter Ego") on Youtube: 75% of original size (was 672x19) - Click to enlarge

Hi Gerry,

still you did not get the point.
If you create a low-poli CC3 character, export as FBX, import in 3DXChange, retarget the bones, export as iAvatar, it works perfectly in iClone.
So, when you say "The FBX export is not intended to be used in iClone" that's wrong: FBX works fine in iClone after being converted through 3DX.
Now, having a little experience (about 25 years...) in SW programming, I can tell you that there is no one single bit of difference between exporting a reduced mesh to FBX format or just exporting it as iAvatar: it is just a different format.
That's what I am asking to RL: to provide a direct export to iClone directly in iAvatar format.
Not rocket science...

Cheers

  Roberto



My PC:
OS: Windows 10 Pro English 64-bit / CPU: Intel i7-9700 3.6GHz / MB: ASUS ROG Strix Z390  RAM: 32GB DDR4 2.6GHz / HD: 2TB+3TB  /  SSD: 2x512GB Samsung 860 EVO + 1x2TB Samsung
VB: Palit GTX2080 TI GamingPro 11GB / AB: embedded in the MB and VB (audio from the MOTU M4 I/F) / DirectX: 12

The FBX export is not intended to be used in iClone, it is for Game software. At the moment the only way to get low poly characters in to iClone is by using the Reduce Wearables Mesh option.

Remeshed characters do not work in iClone at the moment and therefor this option was removed by the Development team for the present.


Gerry

---

System: Win 10 Pro (21H2), Asus X99-E WS, CPU i7-5930K -3,5 GHz, 32 GB DDR4 2666-16 RAM, NVidia GTX 1080 Ti GPU - 11 GB VRAM(Driver Studio-536.99), Samsung 850 Pro 512 GB SSD, 6 TB HD storage.

The Remesh function does not work with iClone, and you can not export a Remeshed iAvater. This function is only available for Game Characters.

Gerry,

this is the current status and we know, but my point is different: is it possible make the low-poli readable by both 3DX and iClone without the bone remapping ?
Because the skeleton structure does not change, so, what does it prevents 3DX to read it as an already rigged character, or transferring the low-poli directly to iClone ?
My request is to enable these features.
If you know precisely the SW code used by RL and can demonstrate that it is really not possible at all, I will withdraw my request, otherwise, pls, let's not jump to conclusions.

I believe many people here bought the Pipeline extension in order to generate low-poli crowds also for iClone and would appreciate an easy way to do that...

Cheers

 Roberto



My PC:
OS: Windows 10 Pro English 64-bit / CPU: Intel i7-9700 3.6GHz / MB: ASUS ROG Strix Z390  RAM: 32GB DDR4 2.6GHz / HD: 2TB+3TB  /  SSD: 2x512GB Samsung 860 EVO + 1x2TB Samsung
VB: Palit GTX2080 TI GamingPro 11GB / AB: embedded in the MB and VB (audio from the MOTU M4 I/F) / DirectX: 12

Exactly the same problem here, with 2 and, I was hoping it wouldn't occur, in 3 as well. Can't use :(

EDIT: Solution to this problem is download the program called Display Driver Uninstaller (Link Here), follow the instruction on cleaning out your old drivers, then reinstall the latest graphics drivers for your card and voila! Fixed.