klinzey
-
Posts
2,534 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by klinzey
-
-
What application are you using to open the exported MVR?
Have you tried 2022 SP3? -
You no longer import a symbol into the catalog, you can use the symbol directly.
Both tools work basically the same way.
https://university.vectorworks.net/mod/page/view.php?id=943The video shows you how to use the mode bar to select the symbol mode from the tool bar at about 23sec fro the speaker and then selecting the symbol from the drop down.
You can also do it from the OIP of the Speaker once placed.
Place the speaker and then make sure the Source is set to Symbol.
Pres the Select Symbol button to select the symbol.
If you change Source to Catalog you will get a mollified version of the speaker symbol you selected.
- 1
-
This is a little bit of a hack but I think it still works. Convert the object handle to a string then to a number. Lower numbers are at the bottom of the stack, higher numbers at the top? I don't remember if this works across layers or not.
-
Use the symbol mode rather than the catalog mode.
-
Currently there is no way to link a Vectorworks symbol.
That functionality is something we are looking into as an improvement in a future version. -
What you are trying to do will not really work because of the nature of a PIO.
When a PIO is reset the PIO starts as an empty container and redraws everything, so when you put an object in the PIO container it will exist but will deleted when the PIO receives a reset event.
In order to do want you want you will need to add the selected geometry to the Profile Group of the PIO and then have the PIO copy the geometry from the Profile Group into the main PIO during the reset when the main PIO code is run. -
No, The photo metric tools do not know about the rendered light at all. The on/off status and intensity percentage of the light is irrelevant as far as the photometric objects are concerned.
Most people use the "Draw Beam" option if they want to be selective about which lights are or are not included in the calculation.- 2
-
Fixture Mode is automatically looked up by using the Instrument Type supplied by the Light Info record. It will automatically do a name match.
If there is no match found the Fixture Mode will be set to None.
The GDTF mode is set to None unless it it set manually in the Tool Bar of the lighting Device or the OIP. -
In your template file Open Spotlight Preferences > Parameters and select Settings: <Spotlight> Click OK and see if that resolves your issue.
The Fixture Mode parameter is hidden in your template file so the made may be getting set automatically but you can't see it.
I've also seen issues where over time adding, removing or reordering parameters causes some controls to be improperly disabled till the default OIP is restored.
-
In order to stay consistent with export to visualizers and consoles the Number of Channels is determined in this order, GDTF Mode, Fixture Mode then the Light Info Record.
When the Number of Channels is determined by the GDTF Mode or the Fixture Mode the Number of Channels field will be disabled.
If you want to manually set the number of fields you will need to set the GDTF Mode and Fixture Mode to None. -
The photo grid does not pay attention to the actual light object. It does not take into account color, shadows, other geometry, layer or class settings.
The calculation is a simple cosine squared falloff based on the candlepower specified in the Light Info Record and the distance between the lighting device and the focus point.
- 1
-
Are you using a style?
What's the length of the soft goods object are you trying to draw?Have you changed any of the default settings?
Usually the issue is with a very long soft goods object or a pleat with that is too small.
If the pleat width is set too small it ends taking a long time to draw because of the number of vertices that are being drawn.There were a few default styles that were shipped with a very small pleat width rather than using the Simple 3D option that have caused issues fro some users.
You can try using the Simple 2D and Simple 3D options to make sure there are no other issues and then check and adjust the pleat width and depth to see if that resolves your issue. -
In Tools > Options > Vectorworks Preferences... > Display enable "Zoom to line thickness (slow)"
- 2
-
You need to render using one of the Renderworks modes to use more than 8 lights.
-
I would call your local tech support. They will be able to provide you additional support and collect some diagnostic information to help you resolve the activation problem.
-
If you are rendering in shaded mode there is an 8 light limit. They may show that they are turned on in the visualization pallet but only the first 8 in the document that are turned on will be rendered.
- 2
-
-
You can not change the graphical layout of the single legend option.
The single label option only gives you a tabular listing of the selected parameters based on the order shown in the dialog. -
Yes, the number of lasers you can use is limited by your license, it's the same limitation as the number of universes.
Educational users are limited to 4 universes and 4 lasers.Users who purchase Vision have unlimited lasers and universes.
-
I looks like you need to change both the "Symbol Definition" parameter and the "Symbol Name" parameter.
You should also call ApplyLightInfoRecord() if you want to update the lighting device with the record information from the new symbol.
Here is a sample script with a test file.
PROCEDURE ChangeSym; VAR SymNameStart, SymNameEnd :STRING; PROCEDURE replaceSymbol(objectHandle :HANDLE); BEGIN SymNameStart := GetRField(objectHandle, 'Lighting Device','Symbol Name'); If SymNameStart = 'Light Instr ETC Source 4 26deg' THEN SymNameEnd := 'Light Instr ETC Source 4 50deg' ELSE SymNameEnd := 'Light Instr ETC Source 4 26deg'; SetRField(objectHandle,'Lighting Device', 'Symbol Name', SymNameEnd); SetRField(objectHandle,'Lighting Device', 'Symbol Definition', Concat(Name2Index(SymNameEnd))); ApplyLightInfoRecord(GetObject(SymNameEnd),objectHandle); ResetObject(objectHandle); SymNameEnd := GetRField(objectHandle, 'Lighting Device','Symbol Name'); END; BEGIN ForEachObject(replaceSymbol,Sel = TRUE); END; RUN(ChangeSym);
-
Yes, there looks like there is a problem on the Mac only with the import dialog.
It's not ideal but you can use a symbol and then change the "Source" to "Catalog".
This will create a generic type based on the attributes of the symbol and create the simple geometry.
You can save this configuration to the catalog if you want to preserve the settings.
- 2
-
@pazworkfornow@gmail.com I would contact Compulite and/or use a 3rd party application to verify that Compulite is outputting data that the computer can read. It looks like it should output the first 512 channels.
I took a quick look at the manual. Make sure you have Art-Net enabled in Compulite.
Art-Net and VC’s must be enabled in Tools Settings DMX Protocol.
You are also using an older version of Vision, the current version of Vision 2022 (27.0.3) so there may also be some fixes to the latest version of Vision. -
@mhersland 2 Things.
Make sure you use the Vision 2022 SP3 installer. We found an issue with the dongle drivers when installed on a new computer that was corrected with the SP3 installer.
Second run the Vision installer again (or run the repair) after you run the MA installer.
The MA installer installs the driver in the wrong location for the 64bit version of Vision.
I think this is your problem. The grandMA.dll in the DmxProviders folder should be 45 KB not 1,003 KB.
-
@ajpen You can also try selecting the option to exporting using 3ds in the export VMR dialog.
The new glTF based format uses a completely different method of texturing (PBR) than 3ds.
Using 3ds may be a faster solution for you while we investigate the problem.
Vision 'No Ambient light"
in Vision and Previsualization
Posted
Which service pack of Vision and Vectorworks are you using?
Make sure your are using at least SP3 of both products.
I now suspect you are not using Vision 2022 SP3.
I think you are actually missing the geometry in Vision because the MVR export in Vectorworks SP3 uses the latest MVR format and you need Vision 2022 SP3 to read the new MVR format.