Show messages:
1-14
15-34
35-48
From: Rich (-RB-)
Ah I'm getting errors uploading and NDA anyway but good to know it might be a video issue, yes just interesting it always seems to pop up with the import of a step...Hopefully just disappears with next beta. If I cut/paste the moi native effected geo in again it clears the problem up if that's any lead
Image Attachments:
001.jpg
From: Michael Gibson
Hi Rich, the error on upload will happen if the file is too large, like more than 10Mb.
For large files you'll need to use a file sharing service like WeTransfer, Dropbox, OneDrive, etc... where you upload the file there and share a link to it. You can e-mail the link to me at
moi@moi3d.com if you want to keep it private.
What operating system are you running on?
If you're on Windows it would probably be a good idea to update your video driver to the latest version from the video card vendor's web site.
- Michael
From: Rich (-RB-)
Hey - sent you a link to file cheers!
From: binfordboy
Hi Michael,
the .fbx import is misisng on this version
Image Attachments:
{5C4E982E-0E08-4092-9F72-5F269C125DAE}.png
From: Michael Gibson
Hi binfordboy, since FBX files contain polygon mesh data and not CAD data, you can write out to an FBX file but not import it in to MoI.
Some more info on that here:
https://moi3d.com/faq#Q:_Why_can_I_export_to_.obj_format.2C_but_cannot_read_.obj_format_into_MoI.3F
The exception to that is if you are doing a sub-d surface conversion. In that case the sub-d importer is on the side pane under SubD > Create > "From file". That can process .obj or .fbx files that contain sub-d control cages.
- Michael
From: SPARTAN-D421 (SIERRA-D421)
Since we're in the middle of June, this particular beta build should be expiring soon, correct?
Asking because I lost track.
From: Phiro
Hi Spartan,
If you look at help/About Moi, you will see Expires on Nov-28-2025
Have fun !
From: SPARTAN-D421 (SIERRA-D421)
> Expires on Nov-28-2025
Got it.
Incidentally, is there a way to set an expiration date for the program so that it won't expire, or is that a server-side thing?
From: Michael Gibson
Hi Spartan,
re:
> Incidentally, is there a way to set an expiration date for the program so that it won't expire, or is that a server-side thing?
Beta versions are set up to expire but the full version won't.
- Michael
From: SPARTAN-D421 (SIERRA-D421)
Allow me to clarify: I meant my question in regards to beta builds.
From: Michael Gibson
Hi Spartan,
re:
> Allow me to clarify: I meant my question in regards to beta builds.
Beta builds are designed to expire.
Once the beta test period is complete there will be a non-beta full release made and the full release versions do not expire.
Thanks, - Michael
From: SPARTAN-D421 (SIERRA-D421)
Right, right. What I'm asking is how the programming handles that bit. Is there a specific file that contains the expiration date and relevant code? And if that's the case, can the files be modified?
Just curious.
(I'd also like to apologize if I seem like I'm not making sense. I struggle with phrasing my queries in a clear manner, as a neurodivergent individual.)
(side note: thanks for adding SVG import/export. I use MoI as part of my workflow for vector graphics and 3D animation, in addition to CAD. Adding SVG import/export makes it much easier, especially since I don't have to worry about any loss of data - and thus, potential loss of detail - when using intermediary formats like PDF like I used to.)
From: Michael Gibson
Hi Spartan,
re:
> What I'm asking is how the programming handles that bit. Is there a specific file that contains the expiration date and relevant code?
Yes, it's part of the code in the main program module file moi_lib.dll .
> And if that's the case, can the files be modified?
Yes, it's possible to do that, it's called "cracking":
https://en.wikipedia.org/wiki/Software_cracking
But usually it's done by people who are distributing pirated versions of the software.
- Michael
From: SPARTAN-D421 (SIERRA-D421)
Gotcha.
Admittedly, I had entertained the idea of cracking - though:
A.) I'd put the kibosh on the idea after thinking it through, and:
B.) it woulda been for personal use anyway had I cracked it,
so there's that.
That said, my line of thinking often goes toward "can it be done" more than "should it be done" and "what are the repercussions thereof" - hence my asking in the first place.
On an unrelated note, is there one more beta build after this, or is V5's public release the next release?
Show messages:
1-14
15-34
35-48
