I want to use this thread to list a few known issues in Version 3.0 which will be corrected in the forthcoming release of Version 3.1.

This is purely for information only, but feel free to add your own comments if you feel that other problems in Version 3.0 need to be addressed.

This thread is purely for reporting issues which are known to be software bugs in Version 3.0. Product enhancement or new feature requests should be directed to the Dynamite VSP Wishlist section.

Dynamic chainage markers in the Swept Object Style Editor and Object Placement Style Editor do not work correctly in 3ds Max 8.0. Changes to spinner values in each editor panel are not reflected in the viewport.

Workaround: Unfreeze the temporary start and end chainage markers from the 3ds Max Command Panel, then select both markers and ensure that the DVSP Explorer panel is open. The marker objects will then react to changes to panel spinner controls.

This issue does not affect Autodesk VIZ or earlier versions of 3ds Max.

Bruce Harfield - 11 January 2007 01:20 PM

This thread is purely for reporting issues which are known to be software bugs in Version 3.0. Product enhancement or new feature requests should be directed to the Dynamite VSP Wishlist section.

Hi Bruce - I’ve noticed when using the DVSP MX Model File Import Panel, non-tangental master strings (and any strings created from them) are not shown up in the import panel. These strings can be imported via the GENIO method, but it would be quite nice to have them show up in the Model File Import Panel.

Not sure if this is a bug or a product enhancement….... hmmm in fact I reckon it’s a bug !!

cheers Mark

Well spotted Mark. It appears that the MX Model File Import Panel in DVSP 3.0 has problems not only with non-tangential alignments, but also any string that was designed at an offset from a non-tangential alignment.

The problem relates to the fact that the string headers for these strings are not currently recognised by DVSP - they are therefore simply ignored. We hope to have a solution for this soon, but in the meantime:

Workaround: Use the GENIO import method in DVSP.

Just to confirm that this one has been solved for Version 3.1.