Wings 3D Development Forum

Here is a software tool that will let you grow ivy on an object... Ivy Generator. It is free for commercial use as well.

oort

A version of this is built into Blender:

http://wiki.blender.org/index.php/Extens...ve/Ivy_Gen

(by "built into" I mean it is distributed as a plug-in that is included in the "trunk" version and maintained by the Blender Foundation.)

An updated made by Ferzan Kanat Aygen to this amazing tool: Ivy Generator 2012

"Ivy generator is now fully multi-core optimized. It is 2.5X faster on a single core and an order of magnitude faster on 4 cores. As far as I can tell it is very stable. I’ve also updated the Qt and OpenGL libraries."



* If you are a Mac user, scroll down the page and look for "3D IvyGen 2012 – MAC “Version"

Micheus,
Thanks for letting us know about this updated version...

When I tried to import the exported ivy into an empty Wings3D file using Wings3D 1.5.3 erlang crashes (erl.exe has stopped working). The "reading" step works but the crash happens during the "importing" step.

Using Wings3D 1.5.2 the same ivy model imports without a problem.

I am running Windows 7 Home Premium 64-bit.

Thanks,
oort

oort, I tested it here in a i5 4GB (only 2GB free) Windows 7 64bit and Wings3D 64bits too.

First I let growing reach these values for Living Branches: 165 from 512
The output file got 64MB of size and I got an Erlang crash. In the Wings3d install folder we find the erlang.dump, I looked for it and I see the problem was related to the amount of memory being requested:

Quote:=erl_crash_dump:0.3
Sat Feb 28 22:05:11 2015
Slogan: eheap_alloc: Cannot allocate 1898305688 bytes of memory (of type "heap").
System version: Erlang/OTP 17 [erts-6.0] [64-bit] [smp:4:4] [async-threads:10]

I tried it again, but now I let it grow only until Living Branches get: 184 from 245
The output file got 30MB and I was able to get it load inside Wings3d. The Ivy object had 227K faces.

I still want to test that in my PC with much more memory.

Micheus,
I think I am running the 32bit version of Wings3D.

Here is the crash file from the wings3d program folder...

Quote:=erl_crash_dump:0.3
Fri Feb 27 21:09:44 2015
Slogan: eheap_alloc: Cannot allocate 317869372 bytes of memory (of type "heap").
System version: Erlang/OTP 17 [erts-6.0] [smp:4:4] [async-threads:10]
Compiled: Mon Apr 7 19:39:50 2014

So, it looks like the same error...

I tried with a smaller ivy.obj file and it imported into Wings3D 1.5.3 without any problem. Why would the file size be an issue in Wings3d 1.5.3 and not in Wings3D 1.5.2? Does Wings3D 1.5.3 use more memory?

I was able to import a 53MB file into Wings3d 1.5.2...

Thanks,
oort

(03-01-2015, 03:44 AM)oort Wrote: [ -> ]Why would the file size be an issue in Wings3d 1.5.3 and not in Wings3D 1.5.2? Does Wings3D 1.5.3 use more memory?

I was able to import a 53MB file into Wings3d 1.5.2...

yeah, that is an interesting question since I don't remember about any changes made to Wings3d that could result on that. Maybe Erlang had. Each Wings3d version was compiled with a different Erlang build.

---

I tested it today in my PC (i7 16GB Windows 64Bit and Wings3d 64bit).
First I crashed Ivy when I put it to Birth the leaves with Living branches: 240 of 2025.

Next try was using Living branches: 243 of 1531
I got an output file huge: 291MB!

I also was able to load it inside Wings3d - it took about 4min and the amount of 2243556 faces.
Easy to navigate, but hard to play with.

oort, thanks for report that.

I did some tests and while it cannot import that image in the .exe program I was able to import it using the same version, but started from the development console.
Now, it's up to the big guys to check that.

Micheus,
I wonder... was something changed in the obj importer between Wings3D 1.5.2 and 1.5.3???

Thanks,
oort

(03-04-2015, 02:13 AM)oort Wrote: [ -> ]I wonder... was something changed in the obj importer between Wings3D 1.5.2 and 1.5.3???

I don't think so - I don't remember about any change on it. Also, as I told, the same 1.5.3 build is able to import the object if I use the dev environment (MinGW). After that, I built an installer ($> make win32) and it was not able to import it anymore.

That remind me I should have tested the file in the Linux version. It probably will work.