Tiles and tile maps
 1-13  14-33  34-49

Previous
Next
 From:  James (JFH)
8663.14 In reply to 8663.13 
Hi Brian

I have returned to original truchet pattern, but with a different approach.
To do this I have created a macro: ArcCenter. Hopefully this will be replaced
with an Arc node with centre, 3 points and tangent options in the near future.

Given that it is covering old ground, I have posted it here rather than
"playing with nodes" thread because I thought it may be a interest to you alone.

Have a great weekend
James

EDITED: 14 May 2019 by JFH

Attachments:

  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  bemfarmer
8663.15 In reply to 8663.14 
Hi James,

I have not studied the node, but made some observations:
Formation takes about 30 seconds +/-.
Apply yields "exception occurred, line 528", and geometry vanishes when node editor window is closed."
But I was able to save the geometry to a .3dm at about 30 seconds+, while node was open.

Note: Slot of a basic math node is remove-able by right clicking on dot.
I need to learn meaning of wire colors...

- Brian
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  James (JFH)
8663.16 In reply to 8663.15 
Hi Brian,

<< Formation takes about 30 seconds +/-......exception occurred, line 528>>

That's odd...For me node generates result in 8 seconds, without error message.
I wonder if someone else might run this nod file and see if issue is repeated:
http://moi3d.com/forum/index.php?webtag=MOI&msg=8663.14

<<and geometry vanishes when node editor window is closed>>

That's true for all (or most) nod files. You need to click "Apply" button to bake out geometry, otherwise it is a preview only.

<< I need to learn meaning of wire colors...>>
Greenish = numbers
Magenta = points
Yellow = objects

James

EDITED: 11 Nov 2017 by JFH

  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  James (JFH)
8663.17 In reply to 8663.15 
Hi Brian,

I have uploaded a revised version of file (attached)
that is reduced in file size by more than a third,
though it does not run any faster (still 8 seconds for me).

Please try, and if error persists, please take screen grab
of error message, so that I might ascertain in which node
the line 528 exception lies.

Thanks
James

EDITED: 14 May 2019 by JFH

  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  bemfarmer
8663.18 In reply to 8663.17 
Hi James,
Time is still about 30 seconds, on my very good Windows computer, with lots of memory and SSD drive.
Apply causes exception, copy attached.
Possiby my nodeeditor setup is different than yours. (?)
File is ~4,144 kb.


- Brian
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Message 8663.19 deleted 14 May 2019 by JFH

Previous
Next
 From:  bemfarmer
8663.20 In reply to 8663.19 
Hi James
After nap, here is the exception.
Copied your extensions. Construct2, max_subdiv..., and basicFunctions slightly different.
Same 30 seconds, same exception upon apply.

- Brian



  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Mike (MGG942)
8663.21 In reply to 8663.19 
Hi, James,

I had some trouble running the nod, but after copying your extension folder, all works properly.
Takes about 7 seconds.

Mike.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Message 8663.22 deleted 12 Nov 2017 by JFH

Message 8663.23 deleted 12 May 2019 by JFH

Previous
Next
 From:  Max Smirnov (SMIRNOV)
8663.24 
I tried to reproduce this error using extensions files from James' post.
Everything works good for me. I tested this node with the last NE release (v.0.97) and with v.0.98 (not released yet).
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  bemfarmer
8663.25 
Very weird.
I renamed nodeeditor directory, and reinstalled version 0.97 to a new nodeeditor directory, and loaded Jame's extension subdirectory.
Same 30 second, error message.
(One time MoI crashed.)


Also tried computer reboot.

Tried loading nod from shortcut key, same result.

- Brian
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Max Smirnov (SMIRNOV)
8663.26 In reply to 8663.25 
Hi Brian,
Right now I tested this node with NE 0.95, 0.97, 0.98 using Win and Mac versions. ~5 seconds. No errors on Apply.
Try to rename moi.ini file and run MoI with default settings.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  bemfarmer
8663.27 In reply to 8663.26 
Thank you Max.

I saved my current Moi.ini file, by renaming it.
I was unable, so far, to locate default Moi.ini, but saw one called MarvsMoi.ini, from 2015, and renamed it Moi.ini.

Success running the truchetSweep3 nod, about 6 seconds., and apply works, 0.97 version.

So something in my previous moi.ini file causes the previous failure...

- Brian
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  bemfarmer
8663.28 In reply to 8663.27 
OK, reverted to my moi.ini file that caused the problem.
My mesh angle was set to 1, (very low).
Changed mesh angle to 15, and now the truchetSweep3 nod works just fine.
(Maybe caused a memory problem with too low a mesh?)

- Brian
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
8663.29 In reply to 8663.28 
Hi Brian, yes a mesh angle of 1 degree will generate very dense display meshes. That would make it likely to run out of memory when dealing with more complex geometry and also take quite a bit more time as well.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Max Smirnov (SMIRNOV)
8663.30 In reply to 8663.28 
Hi Brian,

I set angle to 1 and reproduced this error. I'll add a couple of checks in Output node to avoid this error, but first I'll test NE with upcoming MoI v4.
Also it seems that mesh angle affects on factories performance, so it will be better to use larger values with nodeeditor.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  bemfarmer
8663.31 
Thanks Michael, Max, and James.
- Brian
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  bemfarmer
8663.32 
Under MoI4, my incomplete draft 2D truchet tile (.js) script is lightning fast, with no edge "flicker". :-)
- B
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
8663.33 In reply to 8663.32 
Hi Brian, yeah that will be because of the change in threading model for how scripts are run. In MoI v3 scripts were run in a separate process and used inter-process communication with MoI.exe to retrieve properties and such. That has a fair amount of overhead but it also made it difficult for an errant script to lock up MoI because it could be torn down any time by killing the worker process. In V4 the .js script file for a command is run on the main thread so there's no interprocess communication (same as if in V3 you moved your code over to the .htm file) so a lot less overhead, but it's also easier for it to lock things up if it doesn't behave well like if it just churns away continuously in a loop too much.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged
 

Reply to All Reply to All

 

 
Show messages:  1-13  14-33  34-49