LXSeries Lighting Software

please post the exact steps needed to reproduce the problem, including excerpts from the exported file that illustrate what is exported and what you expect to be exported.

It may be that this is due to an issue with an automated/color mixing fixture with an oval beam. You can try the latest version of LXPlan and see if that makes a difference.

In Qlab send the following message:

/cmd.lxconsole/SUB-1 #v#

OSC Settings should be
OSC Message - Patch ?, 1D Fade, 30 fps, floats, duration of whatever time you want, fade in from 0 to 1.0

Can you email a copy of this plot so I can see what is going on?

If the fixture properties have beamX and beamY included and a drawn symbol of that type is selected, you should have the ability to set the axis. You can also look in the properties table of the Inspector's info tab to confirm if the fixture has a "Beam Axis" property. The only rendering o...

An oval beam can be simulated. Select the light you want to render. In the Inspector's Info table, right-click "Rendering" and choose Edit from the popup menu. In the options dialog, check the Template/Mask button. Click "OK" The rendered beam will then simulate the oval. With th...

What you are looking for is styled text that has paragraph formatting rather than the plain text label. To set the text tool to draw styled text fields, choose Format->Tool->Text Tool->Styled To convert an existing plain text field to styled, select it. Then, choose Format->Convert->Text->To Styled

The toolbar status is usually handled by MacOS. It requires overriding that standard behavior to individually save the toolbar hidden/showing state for each file.

The latest build, 2.7.4 (21308.1), does just that .

There is not really a standardized list of parameters for automated fixtures. For the purposes of LXConsole, you can just use labels that are close. The Manual for the fixture will tell you what the DMX values for things like Auto-Program do. In most cases, they do nothing at zero. If this is the ca...

Does the latest build, 6.7.3 (21224.1), have the same issue?