LightWave 3D® 2019 is Now Available - Official Discussion Thread

BeeVee

ex-LightWave documentation
This update is a surprise!

Would the "Display Scaling" feature enable the development of a future zoom/pan feature in the Camera viewport?
Or a "Zoom Limited Region" maybe?

If the Display Scaling you're talking about is what I think it is, then it's only for the interface elements.

B
 

ianr

Active member
Looks sexy, I say Wavedini here we come ,

great work, from great listening.

Big Kudos to all you Devs
 

mummyman

Medical Animator
That's not a question we can answer for you here, if you mean that you have a discount based on the terms of a previous purchase. You'll need to contact LightWave Customer Services for that information. We're honoring any terms we've previously set forth, but that's not something we're going to try to work through with people on the forums or on social media.

Hmmm I'd like to know the same thing about my upgrade price. But logging into my account and trying to submit a 'contact us' question about my account / version upgrade leads me to an error page. Couldn't get it to work. Would I have to call NT to get this info?

Ha.. .sorry.. didn't see others had the same issue. I was lazy and didn't read.
 

creacon

creacon
Nice to see that the OpenVDB implementation supports a lot of the OpenVDB functionality.

I implemented the filters and the CSG in my own plugin a long time ago, but it would be a lot nicer if I could just create the levelset and let LW (or the user) take it from there. In the video there is also an input/output for a particle system, is this documented anywhere? Are these the "classic" LW particle systems?

thanks

creacon
 
Im having issue with applying for a discount "sorry, an error occurred" and registering the trial... i'll wait a few days #mantears
 

Chuck

NewTek Social Media
Attention LW3DG Marketing: I found out about LW2019 on blenderartists.org an hour ago. Nothing today on Octane LW Forums, CGChannel.com, CGPRess.org, creativebloq.com... Didn't get an email from you...

The email will be going out in a few days. We typically do a rollout over time, such that services can keep up with the demand. Yesterday was press release to press contacts, public announcements on our forum, social media and blog. We also appreciate when members of the community share to the locations they frequent to help the news spread further.
 

bitshift

designer
Nice to see that the OpenVDB implementation supports a lot of the OpenVDB functionality.

I implemented the filters and the CSG in my own plugin a long time ago, but it would be a lot nicer if I could just create the levelset and let LW (or the user) take it from there. In the video there is also an input/output for a particle system, is this documented anywhere? Are these the "classic" LW particle systems?

thanks

creacon

Yes the particle system in OpenVDB nodes input/outputs uses the "classic" LW particle system with position, size, velocity, enable, etc. A particleFX system can be also selected as a source.
 

creacon

creacon
Thanks,

I already have functionality in my plugin that copies my own buffers to a LW particle system, and I know how to create a node input/output. But where can I find the SDK docs for that?

creacon

Yes the particle system in OpenVDB nodes input/outputs uses the "classic" LW particle system with position, size, velocity, enable, etc. A particleFX system can be also selected as a source.
 

bitshift

designer
Thanks,

I already have functionality in my plugin that copies my own buffers to a LW particle system, and I know how to create a node input/output. But where can I find the SDK docs for that?

creacon

We will get those added to the docs.
The nodes use a custom ID for vendorID and typeID.
LWID particleSystemID = LWID_('P', 'S', 'Y', 'S');
outputfuncs->createCustom(nodeid, NOT_CUSTOM, "Particle System", vendorID, particleSystemID);
linputfuncs->createCustom(node, NOT_CUSTOM, "Particle System", NodeInputEventF, vendorID, particleSystemID);

The other LWIDs.

LWID vendorID = LWID_(' ', 'V', 'D', 'B');
LWID typeID = LWID_('X', 'K', 'C', 'D');
LWID gridID = LWID_('G', 'R', 'I', 'D');
LWID vectorgridID = LWID_('V', 'G', 'I', 'D');
 

jaf

New member
Kind of sad day for me. I'm on a fixed income and a hobbyist and can't afford (justify) the $395 now, so then is 2020 comes out next year it would likely be $995. An then I get the Allegorithmic is now Adobe email......
 

creacon

creacon
Exactly what I was looking for :) I'll give it a try.

creacon


We will get those added to the docs.
The nodes use a custom ID for vendorID and typeID.
LWID particleSystemID = LWID_('P', 'S', 'Y', 'S');
outputfuncs->createCustom(nodeid, NOT_CUSTOM, "Particle System", vendorID, particleSystemID);
linputfuncs->createCustom(node, NOT_CUSTOM, "Particle System", NodeInputEventF, vendorID, particleSystemID);

The other LWIDs.

LWID vendorID = LWID_(' ', 'V', 'D', 'B');
LWID typeID = LWID_('X', 'K', 'C', 'D');
LWID gridID = LWID_('G', 'R', 'I', 'D');
LWID vectorgridID = LWID_('V', 'G', 'I', 'D');
 
The node editor aa is very welcome! I wasn't expecting to have happy feelings about grid snap, but that's really nice in nodal.
 
Top Bottom