So I have to weigh that (the 'absolutely zero benefits to a lot of people') against the amount of work required, and that's what makes it not a good 'bang for the buck' type of work for me to focus on as a priority right now. That kind of work is actually somewhat dangerous for me to dig into because it involves a huge amount of work and then at the end of all that work what pops out the end is actually for a lot of people no different than what I had before, because the 64-bit version will produce absolutely zero benefits for people who are not dealing with huge data.

It will be similar in some sense to producing a new operating system version, and right now I've basically spent the past 6 months already doing that similar kind of thing to produce the Mac version already, so I'm not really enthusiastic about turning right around and doing another generally similar type of work right away. It will be a pretty major effort to do it since it will involve an across the board update to a lot of things including using a new compiler, and updates to all libraries. Probably at some point yes, but it's likely to be quite a few years away. > A cheeky question - is a 64bit version ever likely? Setting the 'Mesh angle' to a rougher angle like 25 degrees and unchecking 'Add detail to inflections' will make for a somewhat rougher looking display but also lighten up the density of the display meshes and that can help reduce memory consumption by quite a bit on more complex models.īut still it is somewhat doubtful that a huge 375 mb file will be able to be loaded all in one single chunk, you will still likely need to have it broken into a couple of pieces instead.

You can lighten the memory load somewhat by changing a setting to use a rougher display mesh, that's a setting under Options > View as described here: There is no one specific limit, since it depends on what kinds of things are in the file - for example like AW mentions above if there are a lot of block instances inside the file that will balloon into a much larger size in memory at load time as they each become an individual object at load time into MoI right now.Īlso if the object has a whole lot of little tightly curved pieces in it, that will consume more memory for display mesh generation when it is loaded. > Does MOI have an upper limit of the file size it can import? You will probably need to get that exported out from whatever application is writing it into a few separate files instead of one single gigantic file.

MoI is a 32-bit program so it's only actually able to use 4GB of your memory and a 375mb file is quite large in size. Hi Matt, MoI is just plain old running out of available memory when that happens.

.stp viewer for mac