> On xp64, with 8 gig's, MoI stop meshing when reaching 3.3 ~ 3.4 mega
Yeah that is not unusual because the full address space to a program is not completely empty, other stuff such as the program code itself is in that same area.
Also the available address space can get diced up into sort of "fragments" where there isn't a big single block of address space available for something that needs a big single chunk.
Similarly if you have it at the default 32-bit 2Gb/2Gb split you will tend to actually max out more around 1.6 Gb of actual use.
Michaels last program "RHINO" has thousands of plugins written for it. It also allows scripting which has "hundreds of thousands" of scripts written for it.
These are applications that allow the user and other "developers" to customize things, sometimes for a "onetime thing only".
The software has A "Base" documentation, but if you want to delv into the realm of developer, it is unrealistic for the software company to try and control this.
As a beta tester, you'll see things fly by that arent documented yet (possibly ever). Something written only for "JIM" who need a light to come from a specific "Angle".
This isnt functionality of the software. Only the ability of it to be scripted.
Everything that is part of the "custom scripts" library that you use can be done with a simple default install of MoI! The scripts are just different way's it can be done (An infinate amount).
Are you going to add "Llama Mode" as a shortcut key??? I have! When my brain locks up and the juices stop flowing, I click Llama mode, LMAO, then contiue on to produce. Others may have no need for "Llama Mode".
Quote: "Have you told Mr Obama that I am available for consultations?"
I tried to get through to his office but he was unavailable. He was busy documenting what he saw going on outside the whitehouse window!
6.00 am - dog barked.
7.26 am - michelle needed sugar handed to her for her coffee.
8.00 am - man on lawn whomb I dont know yet.
9.00 am - ignored call from some guy named Burr!
10.00 am - back to looking out the window.
11.00 am - ????
:)
Hi Brian, well it seems like we've been through the same discussion on shortcut keys and scripting several times before, so I wanted to give you a very clear and thorough answer about what to expect in this area.
This situation will probably not be changing anytime soon, so if/when this comes up again I'll just refer back to that answer and we won't need to have a long drawn out discussion on it anymore.
I suppose it's like the "CARRARA" app that allows a user to define new "Shaders" and "Materials" and then in the Carrara Beta Forum somone keeps asking the developer..."I saw you make this great Grey Brick Material that this guy needed for his wall model"..."Why do I need to be bothered with all this refraction, bumpmap, halo mumbo jumbo? Cant you just call it Grey Bricks and put it all on a menu? I mean, we're not all rocket scientists, so having to know all these settings to make a material seems odd to a normal user. Sure I see 3rd party developers making all kinds of materials, shaders and objects but how can I keep track of all these things? Cant you just INCLUDE them all in the application and let me decide which ones I want to use?
@Burr : Thx for the address of the test Robot
My result with a very old computer (6 years old)without multi core :)
Ati radeon 9200 (128 ram video) XP Amd 2600 1.91 GHZ
V1 = 35 seconds
v2 = 6 seconds
Not so bad ;) But I have something running in background so more results soon!
If I * 10 the robot moving in V1 is very hard
In V2 that works fine (thx Proxy)
That's a good timing improvement even on your older computer Pilou!
Yes, many of the optimizations will also help to speed meshing up quite a bit even on a single core CPU, it just gets magnified by a greater factor if you do have multi-core.
just a little detail, but the first time you export a mesh I notice that divide larger than type is empty (when it's supposed
to be on 'curve' by default.
[EDIT]By the way, mine still came up curves! Maybe you added the new switches to your ini without setting it because my ini doesnt have all the new switches in it by default![EDIT]
The think is, dispite the fact angle is empty, moi chose 12 as default value.
However DivideLargerThanApplyTo= return an blank value, where I suppose 'curve' should showed by default ...
Is the value to put there. What threw me was the case sensituve switch! In the Ui It's listed as "Curved" and that doesnt work. Checked the meshdialog file and saw it with lower case and it works.
