11
News:
Recent Posts
12
Feature Requests / Re: Save camera position
« Last post by thor6136 on November 11, 2020, 09:26:37 am »Is it possible to set FOV to newly created cameras?
13
Community Help / Re: Custom UI/Custom Menu
« Last post by rubberDuck on November 05, 2020, 06:45:37 pm »Perfect!
Thank you!
Thank you!
14
Feature Requests / Re: Save camera position
« Last post by thor6136 on November 05, 2020, 11:20:01 am »Love it, awesome! Exactly what i was looking for 
And there is also a cycle camera command as well, for multiple cameras, if anyone will have similar question.
And there is also a cycle camera command as well, for multiple cameras, if anyone will have similar question.
15
Feature Requests / Re: Save camera position
« Last post by IStonia on November 05, 2020, 11:17:18 am »You can do this.
1. Adjust to the view you want.
2. Geometry > Create > Add Camera. Create the camera with camera aligned to current viewport camera option.
3. Run "Align To Camera" command whenever you want.
1. Adjust to the view you want.
2. Geometry > Create > Add Camera. Create the camera with camera aligned to current viewport camera option.
3. Run "Align To Camera" command whenever you want.
16
Feature Requests / Save camera position
« Last post by thor6136 on November 05, 2020, 10:55:26 am »Would it be possible to save current camera position and then whenever activating a command resetting camera position to previously saved?
For example:
Step 1: save current camera position: press shift + f1
Step 2: move camera around, do whatever
Step 3: press f1 and it snaps camera to previously saved position
Whenever save current camera position would get pressed it would rewrite previously saved position.
This is very helpful if I am designing from a particular camera angle and I can check how it looks when I add new stuff
For example:
Step 1: save current camera position: press shift + f1
Step 2: move camera around, do whatever
Step 3: press f1 and it snaps camera to previously saved position
Whenever save current camera position would get pressed it would rewrite previously saved position.
This is very helpful if I am designing from a particular camera angle and I can check how it looks when I add new stuff
17
Community Help / Re: Custom UI/Custom Menu
« Last post by IStonia on November 05, 2020, 10:10:41 am »Try this
http://www.digitalfossils.com/Download/NVil-Nov-05-20.rar
1.2. The options are added.
3. Select the lattice then open the Box tool to alter the subdivision. Regardless what deforming stage you are at.
4. Not possible.
http://www.digitalfossils.com/Download/NVil-Nov-05-20.rar
1.2. The options are added.
3. Select the lattice then open the Box tool to alter the subdivision. Regardless what deforming stage you are at.
4. Not possible.
18
Community Help / Re: Scaling affect memory usage?
« Last post by rubberDuck on November 02, 2020, 09:40:07 pm »Yes, that most definitely shouldn't have any impact on memory.
Each vertex has a position defined by a 3D vector, which consists of three floating-point numbers defining a vertex position in space. Each one of those values has a constant amount of bits allocated in your computer's memory. It's predefined, so it doesn't matter if you scale your object by 0.0001 or 10,000 - the allocated memory for that variable (say, a vertex position on X axis) will always remain the same.
The only problem you may encounter with scaling, is the loss of precision when you cross the limits provided by 32-bit or 64-bit floating-point numbers - you will start getting strange "artifacts" all over your mesh (it will deform in unexpected ways).
Each vertex has a position defined by a 3D vector, which consists of three floating-point numbers defining a vertex position in space. Each one of those values has a constant amount of bits allocated in your computer's memory. It's predefined, so it doesn't matter if you scale your object by 0.0001 or 10,000 - the allocated memory for that variable (say, a vertex position on X axis) will always remain the same.
The only problem you may encounter with scaling, is the loss of precision when you cross the limits provided by 32-bit or 64-bit floating-point numbers - you will start getting strange "artifacts" all over your mesh (it will deform in unexpected ways).
19
Community Help / Re: Custom UI/Custom Menu
« Last post by rubberDuck on November 02, 2020, 09:10:22 pm »FFD, at last!
If I may, I have several ideas on how to improve this tool:
1. Can you add a feature in Open Box Tool# that would allow us to resize and reposition the lattice box to match the bounding box of selected objects if at least one object is selected? If no objects are selected, place the deforming mesh at the world origin, as it happens now.
2. Another option in this tool which I think would be useful, is a checkbox to match Lattice rotation to rotation of a selected object. If multiple objects are selected, use their average rotation.
3. Would it be possible to modify the number of edges of the lattice object in real-time, after it's been bound to objects that we intend to deform?
4. Extension of point 3 - maybe allow insertion of edge loops in FFD mesh using standard NVil tools (like insert edge loop)?
1 and 2 alone would save a lot of time because usually you want the deforming mesh to match the bounding box size, position, and optionally: orientation, of deformable objects.
If I may, I have several ideas on how to improve this tool:
1. Can you add a feature in Open Box Tool# that would allow us to resize and reposition the lattice box to match the bounding box of selected objects if at least one object is selected? If no objects are selected, place the deforming mesh at the world origin, as it happens now.
2. Another option in this tool which I think would be useful, is a checkbox to match Lattice rotation to rotation of a selected object. If multiple objects are selected, use their average rotation.
3. Would it be possible to modify the number of edges of the lattice object in real-time, after it's been bound to objects that we intend to deform?
4. Extension of point 3 - maybe allow insertion of edge loops in FFD mesh using standard NVil tools (like insert edge loop)?
1 and 2 alone would save a lot of time because usually you want the deforming mesh to match the bounding box size, position, and optionally: orientation, of deformable objects.
20
News and Updates / Re: Nvil Update Oct 29 2020
« Last post by kevjon on November 02, 2020, 09:35:30 am »Quote
Check this, http://digitalfossils.com/nvil-forum//index.php?topic=5020.0.
Thanks Istonia, that's a very useful feature indeed, time to do some more customization I think !