PDA

View Full Version : LightWave 3D 2018.0.3 Update is Posted!!!



Chuck
03-29-2018, 04:15 PM
LightWave 3D 2018 users: the third stability update, 2018.0.3 is ready in your account:

LightWave 3D Registration Account (https://www.lightwave3d.com/login/?next=/account/)

Chris S. (Fez)
03-29-2018, 04:26 PM
Thank you!

MAUROCOR
03-29-2018, 04:59 PM
Great news, thank you Chuck! ;)

gjjackson
03-29-2018, 05:58 PM
Oh Great, Now you tell me. I just installed the last version a couple hours ago after checking the update page a few hours ago.

Bitboy
03-29-2018, 06:09 PM
Great, thanks Chuck!

MonroePoteet
03-29-2018, 06:48 PM
Yay! Will upload late tonight and install. Looking forward to it!

mTp

Revanto
03-29-2018, 06:59 PM
Thanks, Chuck. Could you post up a changes list or at least a link to one, please?

Thanks.

Rev. :p

pixym
03-29-2018, 07:03 PM
Thanks Sir Chuck.

raymondtrace
03-29-2018, 07:10 PM
Thanks, Chuck. Could you post up a changes list or at least a link to one, please?

The change list always appears next to the download link in your account.

c.1
03-29-2018, 07:11 PM
:rock:Fkn A Chuck

Marander
03-29-2018, 07:33 PM
Nice! Thanks for providing frequent updates!

Oldcode
03-29-2018, 07:34 PM
Cool! It says they fixed the Make Path tool! Hurray! I can't wait to try it! :D

Revanto
03-30-2018, 12:10 AM
The change list always appears next to the download link in your account.

Yes, but it would be nice not to have to login to something to see what has changed.

Rev.

vipvip242
03-30-2018, 12:11 AM
thanks a lot

Mr. Wilde
03-30-2018, 07:13 AM
Thanks!

With the frequency of releases, I wish LightWave was a self-updating software. Every time I have to install it again, copy all the plugins and configs I use. LW should be able to install updates in the same folder.

JamesCurtis
03-30-2018, 07:27 AM
That's fine EXCEPT that, if you did discover a problem with the self-updated version [a plugin incompatibility problem, etc.], you'd have to reinstall it to an earlier state [which may not be possible with self-update].

robertn2k
03-30-2018, 07:39 AM
Thanks!

With the frequency of releases, I wish LightWave was a self-updating software. Every time I have to install it again, copy all the plugins and configs I use. LW should be able to install updates in the same folder.

Or at the very least give you the option. I have to update 40 seats in our iMac lab . . . one at a time after every update. It's wonderful that they keep bug fixes coming but have to redo all the plug-ins is a major issue.

creacon
03-30-2018, 08:20 AM
Don't know about Mac, but on PC we used to install 1 version on the server with redirected (read only) configs.
All the workstations just had shortcuts to that one install. Upgrade 50 workstations was 5 minutes max.

creacon


Or at the very least give you the option. I have to update 40 seats in our iMac lab . . . one at a time after every update. It's wonderful that they keep bug fixes coming but have to redo all the plug-ins is a major issue.

TheLexx
03-30-2018, 08:24 AM
It's a trade-off of pros and cons, but full offline manual control is ultimately best in my view. But c'mon, from too much silence to too much updates is just great.

:)

Marander
03-30-2018, 09:05 AM
Or at the very least give you the option. I have to update 40 seats in our iMac lab . . . one at a time after every update. It's wonderful that they keep bug fixes coming but have to redo all the plug-ins is a major issue.

If you upgrade that many installations you should find a way to automatize the deployment.

But yes I agree, updating LW for stability / maintenance releases should be inplace or offer the option. But that of course requires additional efforts in packaging the software.
For example the Vue 2016.4 to 2016.5 update is done much faster (inplace, within seconds) and that's even a feature release.
However for me I find it more important that they deliver fixes in a timely manner than the installation procedure itself.

And I'm sure it offers a silent install too and with a few scripting you can automatize the whole thing easily.

Edit - here you go

LightWave 2018.0.3 2018.0.3
Usage:

--help Display the list of valid options

--version Display product information

--unattendedmodeui <unattendedmodeui> Unattended Mode UI
Default: none
Allowed: none minimal minimalWithDialogs

--optionfile <optionfile> Installation option file
Default:

--debuglevel <debuglevel> Debug information level of verbosity
Default: 2
Allowed: 0 1 2 3 4

--mode <mode> Installation mode
Default: qt
Allowed: qt win32 unattended

--debugtrace <debugtrace> Debug filename
Default:

--installer-language <installer-language> Language selection
Default: en
Allowed: sq ar es_AR az eu pt_BR bg ca hr cs da nl en et fi fr de el he hu id it ja kk ko lv lt no fa pl pt ro ru sr zh_CN sk sl es sv th zh_TW tr tk va vi cy

--prefix <prefix> Installation Directory
Default: ***unknown variable platform_install_directory***/NewTek/LightWave_2018.0.3

--expand_python_PySide <expand_python_PySide> PySide 1.2.4
Default: 1

--expand_python_pywin32 <expand_python_pywin32> pywin32 2.19
Default: 1

--expand_python_WinPDB <expand_python_WinPDB> WinPDB 1.4.8
Default: 1

--expand_python_MySQLdb <expand_python_MySQLdb> MySQLdb 1.2.5
Default: 1

--expand_python_Nose <expand_python_Nose> Nose 1.3.8
Default: 1

--expand_python_NumPy <expand_python_NumPy> NumPy 1.9.2
Default: 1

--expand_python_runtime <expand_python_runtime> Expand Python Runtime
Default: 1

--register_lws <register_lws> LightWave Scene (.lws)
Default: 1

--register_lwo <register_lwo> LightWave Object (.lwo)
Default: 1

--register_extensions <register_extensions> Register File Extensions
Default: 1

--node_advanced <node_advanced> Would you like to configure advanced options for the Network Render Controller Service?
Default: 0

--node_operation_type <node_operation_type> Select the NRC Service operation type
Default: task_tray
Allowed: task_tray service

--node_account_type <node_account_type> Select the NRC Service account
Default: user
Allowed: user network system

--nrc_account_name <nrc_account_name> Account Name*
Default: .\Marander

--nrc_account_pass <nrc_account_pass> Account Password*
Default:

--logoutput <logoutput> Output Destination
Default: console
Allowed: console file

--loglevel <loglevel> Logging Level
Default: warn
Allowed: info warn error

--logfilename <logfilename> Log file
Default:

--fallbackport <fallbackport> Base fallback port
Default: 29572

--nodeid <nodeid> Network Render Controller Service Identifier
Default: M-ARTSTATION NRC Service

--Setup <Setup> Setup Type
Default: Typical
Allowed: Typical Screamernet Custom

raymondtrace
03-30-2018, 10:24 AM
Yes, but it would be nice not to have to login to something to see what has changed.

Didn't you need to log into this forum?

Didn't you need to log into lightwave3d.com to download the update...from the link Chuck posted at the start of this thread?

The internet is getting really hard these days... :p

David_CGC
03-30-2018, 09:40 PM
Thanks!

With the frequency of releases, I wish LightWave was a self-updating software. Every time I have to install it again, copy all the plugins and configs I use. LW should be able to install updates in the same folder.

It's probably a terrible idea for any number of reasons I'm happily ignorant of, but I've started duplicating the files in LW's Application Support folder (not sure what the Windows equivalent location is), complete with renaming all the files that include the version number. I haven't run into a problem so far, and it's saved me a lot of tedious exporting and reloading of keyboard and menu files.

It's a simple enough operation that I would imagine it could be folded into the installer (with the added benefit that the devs know what's changed, and could either not copy over, convert, or update any config files that are different).

ianr
03-31-2018, 09:27 AM
New update :

LightWave 2018.0.3 (Build 3066) Final Release Change Log - Mar 29, 2018

Corrected the Windows Installer script to restore the 'Custom' component-selection page.
Corrected handle drawing on the Feedback Agent's 'enhanced' capture mechanism for displays with vertical resolutions lower than 1200.

LB-834 in a different way. The old fix was causing significant slowdowns in switching layers in Modeler, as it invalidated the meshes every time the current layer was switched.
LB-4666 Auto scene saving resets VPR
LB-4667 If a previously added Scene task is no longer valid when the NRC Controller starts -- i.e., scene file, content or output path no longer exist -- it will not be restored to the Task list.

LWB-3045 F10 render fails silently - if image saving fails
LWB-3456 Motion render buffer did not work unless motion blur was on in camera and there was actual deformation at the start time of the frame.
LWB-3476 The NRC Service now checks all acceptable plug-in paths when validating the environment.
LWB-3494 'visible to camera' still able to be selected for environment light and point light.
LWB-3507 Corrected a typo in a warning dialog's text message.
LWB-3512 Crashes when trying to make a path.
LWB-3518 Can't change Motion Blur sub-frames value using the keyboard
LWB-3527 Fixed slowdown when switching layers in Modeler. Meshes are no longer being invalidated when switching layers. Instead syncs for VMAP changes/add/remove are propagated to all meshes. Mesh validation is then done when layer switching to it, and only if needed, instead of always invalidating the mesh.
LWB-3541 Camera imported with alembic flips rotation if we move any other item
LWB-3542 Gizmo Transform
LWB-3549 heatshrink is not working correctly with tablet
LWB-3553 rendering status in mac icon app bar only show blank rendering status
LWB-3559 Unaffected by Fog
LWB-3561 LightWave 2018.0.2 TweakTool broken
LWB-3566 Splinebridge fixed when the first selection outline points are less than the second selection outline points
LWB-3569 Save All Objects command doesn't save objects two folders deep
LWB-3572 GUI Checkmark/Name Bug in MDD Multi-Loader
LWB-3573 MDD Multi-Baker vs Multi-Loader File Name Discrepancy
LWB-3574 Crash on VPR or render. OpaquePolygon function wasn't copying vertexIndexes.
LWB-3577 Volumetric radius smaller than 5 mm isn't rendered. Fix determinate check in matrix operations.
LWB-3584 Glow Image Filter "Intensities" Table Heading Position Locked
LWB-3590 surfid = surfInfo->byObject(objinfo->filename( objid )); returns a null surface pointer
LWB-3594 ray cast nearest point index or polygon index causes crash to desktop. fix invalid access.
LWB-3600 Shiny black hair with HDRI environment Light
LWB-3601 Raycast crash
LWB-3604 Changing color in scene editor doesn't refresh
LWB-3608 FFX Crash. fix for bezier curves.
LWB-3610 RayClosest. Fix invalid access.
LWB-3613 Make initial output render buffer "Final Render" checked ON by default (Save enabled).
LWB-3615 Localize issue.
LWB-3618 Mouse dragging DOF circle values not smooth
LWB-3620 Particle system crashes immediately
LWB-3621 The beauty buffer from external renderers is not saved while F10 rendering
LWB-3623 Preview playback not working
LWB-3624 Spotlight cone angle sharpness. restore previous behavior for spotlights with area.
LWB-3628 FX Browser, property windows load on top of each other, crash on close
LWB-3637 With a tablet, copy/paste colors, can change the color drastically. Changed workflow to - CTRL RMB = Copy Swatch, ALT RMB = Paste swatch
LWB-3642 Customize Interface Color - Background splash gives "Can't find Targa Plugin"
LWB-3648 Switch node of the Multi Switch does not control.
LWB-3649 Arbitrary render does not work. Single, Arbitrary and Keyframe renders will now render the current frame on F9.
LWB-3653 Animation End Beep no sound.
LWB-3659 render buffers not copy/paste to Photoshop
LWB-3668 Particle Emitter Type "Object-Normals" and "Object-Verticies" are not right
LWB-3675 Allow querying the ID of which node-editor is open
LWB-3683 SSS for primitive shapes is broken. FIx SSS and odd shadow clipping
LWB-3700 Hue value decreases each time it's viewed in the text edit field (Surface Editor)

LWF-1485 HSV color swatch in different places has different representation

Shloime
04-03-2018, 02:44 AM
Now back to the config files:
I guess I am not the only one to reconfigure menu layouts, keys and add some plugins. So with every iteration we get new config files and would have to start all over again.
My way was to just rename the old configs (LWM2018.0.1 to LWM 2018.0.2). Is that a valid way?
On closer examination of the configs I noticed that all the entries are mixed up between versions. Is that deliberate to make it harder to spot changes? Are there any changes at all?
Can I just copy all the menu entries from one config to the other? Or what is YOUR way of keeping the update work to a minimum?

rustythe1
04-03-2018, 04:16 AM
Now back to the config files:
I guess I am not the only one to reconfigure menu layouts, keys and add some plugins. So with every iteration we get new config files and would have to start all over again.
My way was to just rename the old configs (LWM2018.0.1 to LWM 2018.0.2). Is that a valid way?
On closer examination of the configs I noticed that all the entries are mixed up between versions. Is that deliberate to make it harder to spot changes? Are there any changes at all?
Can I just copy all the menu entries from one config to the other? Or what is YOUR way of keeping the update work to a minimum?

Problem is if there were changes that affect configs from point to point, its best to start clean, and those configs may be pointing at directories etc from the previous install, with menus you can just save menu branches, plugins, you only need to scan the directory once so its a 5 second job, (use edit plugins rather than add as you get the scan directory option that will add everything in the folder you point too)

raymondtrace
04-03-2018, 07:29 AM
I use WinMerge (or pick your favorite diff tool) to compare config files between versions, pulling over any particular lines from the old config that should appear in the new config.

Oldcode
04-03-2018, 07:43 AM
LWB-3512 Crashes when trying to make a path.

I've been testing the Make Path tool and so far it has not crashed once!

:dance: :beerchug: :jam: :D :rock: