Blender instances "patch" for the unofficial exporter
@Kavorka : When importing an object, it is often with high specularity and not very visible, over all if it is small or displayed at some distance. Your object may be there... Try to play with environment lighting (rotate the sun direction to seek a reflection ).
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
When I just select my single chair node, it is visible and placed where it should be. I attached the scatter node to my geometry group, but then the chair disappears, but the triangle count says its there. My assumption is that the scatter node is scattering incorrectly.
Intel quad core i5 @ 4.0 ghz | 8 gigs of Ram | Geforce GTX 470 - 1.25 gigs of Ram
Currently dupli object write does not work properly with dupli emitter, if you move the emitter from world origin (the object does not get re-centered)kavorka wrote:When I just select my single chair node, it is visible and placed where it should be. I attached the scatter node to my geometry group, but then the chair disappears, but the triangle count says its there. My assumption is that the scatter node is scattering incorrectly.
Else, can you post an example .blend that exhibits this problem (it does not need to have the chair model)
SW: Octane 3.05 | Linux Mint 18.1 64bit | Blender 2.78 HW: EVGA GTX 1070 | i5 2500K | 16GB RAM Drivers: 375.26
cgmo.net
cgmo.net
kavorka wrote:When I just select my single chair node, it is visible and placed where it should be. I attached the scatter node to my geometry group, but then the chair disappears, but the triangle count says its there. My assumption is that the scatter node is scattering incorrectly.
What do you know, I am getting the same thing. The instances are absolutely nowhere to be seen.
Well I can see the problem. The matrices have been exported with a scale of zero.
0.0000000 0.0000000 0.0000000 -0.9810741 0.0000000 0.0000000 0.0000000 -0.0025638 0.0000000 0.0000000 0.0000000 0.3187820
0.0000000 0.0000000 0.0000000 0.9194058 0.0000000 0.0000000 0.0000000 -0.0030427 0.0000000 0.0000000 0.0000000 0.7303052
0.0000000 0.0000000 0.0000000 -0.5681733 0.0000000 0.0000000 0.0000000 -0.0027134 0.0000000 0.0000000 0.0000000 0.1050323
0.0000000 0.0000000 0.0000000 -0.0676142 0.0000000 0.0000000 0.0000000 -0.0086357 0.0000000 0.0000000 0.0000000 0.0124721
0.0000000 0.0000000 0.0000000 0.6799352 0.0000000 0.0000000 0.0000000 -0.0048563 0.0000000 0.0000000 0.0000000 0.0041003
0.0000000 0.0000000 0.0000000 0.5890252 0.0000000 0.0000000 0.0000000 -0.0049298 0.0000000 0.0000000 0.0000000 -0.8827631
(HW) Intel i7 2600k, 16GB DDR3, MSI 560GTX ti (2GB) x 3
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
I've updated the first post with a new version, 0.1.6
* automatic exporting the dupli object mesh(es) now works for dupli-emitters too (the file takes the name of the emitter + "_objects" suffix - since the emitter can have many children)
* transforming the dupli-emitter or the child objects (dupli objects) should result in correct instance transforms. So for dupli-emitters there is no more required that the dupli object is located at parent origin.
steve, kavorka, test this version. If the problem persist, post an example .blend, I haven't yet encountered such problem
* automatic exporting the dupli object mesh(es) now works for dupli-emitters too (the file takes the name of the emitter + "_objects" suffix - since the emitter can have many children)
* transforming the dupli-emitter or the child objects (dupli objects) should result in correct instance transforms. So for dupli-emitters there is no more required that the dupli object is located at parent origin.
steve, kavorka, test this version. If the problem persist, post an example .blend, I haven't yet encountered such problem
SW: Octane 3.05 | Linux Mint 18.1 64bit | Blender 2.78 HW: EVGA GTX 1070 | i5 2500K | 16GB RAM Drivers: 375.26
cgmo.net
cgmo.net
ok, I grabbed the newest file, and everything works perfectly, except, when it scatters my chairs, it scales them down to like a 10th of the size. I applied the scale to my chair and my emiter, but its still happening.
Anyone else get this problem?
EDIT:
Also, I should note that clicking on my chair mesh node shows the chair in the correct scale, also with it connected directly to my group node along side my scene mesh node, it shows the scale correctly, it is only when the scatter node takes effect that it scales down.
Anyone else get this problem?
EDIT:
Also, I should note that clicking on my chair mesh node shows the chair in the correct scale, also with it connected directly to my group node along side my scene mesh node, it shows the scale correctly, it is only when the scatter node takes effect that it scales down.
Intel quad core i5 @ 4.0 ghz | 8 gigs of Ram | Geforce GTX 470 - 1.25 gigs of Ram
Thanks Matej.
Just a side note but it would be nice if otoy can move her ass.
Just a side note but it would be nice if otoy can move her ass.
W10 x64 32GB, EVGA GTX960 - EVGA GTX1060 - OSX 10.12.5 - CORE I5 3.4GHz
A bit better but for some reason I am now getting a scaling factor of 4
4.0000000 0.0000000 0.0000000 0.7299656 0.0000000 4.0000000 0.0000005 1.0117099 0.0000000 -0.0000005 4.0000000 -0.4333910
4.0000000 0.0000000 0.0000000 -0.5470980 0.0000000 4.0000000 0.0000005 0.8958297 0.0000000 -0.0000005 4.0000000 0.8050458
4.0000000 0.0000000 0.0000000 1.1484637 0.0000000 4.0000000 0.0000005 0.4332794 0.0000000 -0.0000005 4.0000000 0.4864346
4.0000000 0.0000000 0.0000000 1.2265090 0.0000000 4.0000000 0.0000005 0.4626582 0.0000000 -0.0000005 4.0000000 0.1166105
4.0000000 0.0000000 0.0000000 0.2858431 0.0000000 4.0000000 0.0000005 -0.3472993 0.0000000 -0.0000005 4.0000000 1.2384622
I've attached the .blend. It really was a bung it together and render job so I apologise for not renaming the objects
4.0000000 0.0000000 0.0000000 0.7299656 0.0000000 4.0000000 0.0000005 1.0117099 0.0000000 -0.0000005 4.0000000 -0.4333910
4.0000000 0.0000000 0.0000000 -0.5470980 0.0000000 4.0000000 0.0000005 0.8958297 0.0000000 -0.0000005 4.0000000 0.8050458
4.0000000 0.0000000 0.0000000 1.1484637 0.0000000 4.0000000 0.0000005 0.4332794 0.0000000 -0.0000005 4.0000000 0.4864346
4.0000000 0.0000000 0.0000000 1.2265090 0.0000000 4.0000000 0.0000005 0.4626582 0.0000000 -0.0000005 4.0000000 0.1166105
4.0000000 0.0000000 0.0000000 0.2858431 0.0000000 4.0000000 0.0000005 -0.3472993 0.0000000 -0.0000005 4.0000000 1.2384622
I've attached the .blend. It really was a bung it together and render job so I apologise for not renaming the objects

- Attachments
-
- instancedcube.zip
- (193.9 KiB) Downloaded 313 times
(HW) Intel i7 2600k, 16GB DDR3, MSI 560GTX ti (2GB) x 3
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
(SW) Octane (1.50) Blender (2.70) (exporter 2.02)
(OS) Windows 7(64)
@steve, kavorka
I suppose its because it doesn't re-scale the "native unit size" correctly. I'll look into it, for now use the default meters.
I suppose its because it doesn't re-scale the "native unit size" correctly. I'll look into it, for now use the default meters.
SW: Octane 3.05 | Linux Mint 18.1 64bit | Blender 2.78 HW: EVGA GTX 1070 | i5 2500K | 16GB RAM Drivers: 375.26
cgmo.net
cgmo.net