Jump to content

Beam multiplier and canela settings saved with v3s file


Recommended Posts

Hi,

Beam multiplier and candela setting don't get saved in the v3s file. Is there a way to save these with the v3s file as every time I open a file I need to readjust these settings along with other settings.

 

Cheers

Link to comment
  • Vectorworks, Inc Employee

I'd have to test, but I think this may be a regression if it is reproducible. I swore all of that information worked in the past. I didn't think we'd changed much in that area so I didn't expect anything to break. I'll try to take a look and see what is going on.

 

What fixture(s) are you testing? Might be best for me to try the same ones JIC. I assume you are using litfiles and not GDTF?

Link to comment

Hey Bbudzon

 

I'm so sorry, my mistake, it does save with the file. I must have got confused when I reimported the MVR file from Vectorworks.

 

In terms of the colour temperature settings, the Thomas 4-light molefay fixture outputs stark white light but the colour temperature setting is on 3000 and changing the setting doesn't change the temperature. Does this setting only work on certain fixtures?

Link to comment
  • Vectorworks, Inc Employee

If the UI is allowing you to change the UI, then it should take effect. There may be a bug in either detecting whether or not the color temp field should be "editable". There may be a bug in the handling of color temperature.

 

My suggestion would be to play around with a fixture whose color temperature is clearly working; such as a S4 19deg. I posted somewhere in these forums recently about color temperatures. Some users seem to think there isn't enough difference between, say, 3200K and 6000K; other users think the difference is too much.

 

If you can find some time to play around with a known working fixture (in regards to color temp) you should see that 6000K is fairly "white" and 3200K is more "amber". Vision does not yet have a white balance setting. If the S4 19deg is working as you expect, I'd go back and test the molefay one more time. If you still believe there is a bug or issue with the content, report back and kick off tickets to the appropriate parties.

Link to comment
  • 4 weeks later...

I can confirm that the colour temperature cannot be adjusted on the Thomas 4-light molefay. They are white, not warm white. What is the best way to report a fixture bug?

Link to comment
  • Vectorworks, Inc Employee

If you have access to JIRA, you should file it there. The advantage of having this access (which is restricted to BETA users I believe) is you kind of get updates on the report and will see when it has been resolved and at what build number.

 

Otherwise, I'll make a note to open a report in JIRA myself; one that references this forum post.

 

It's not clear to me yet whether or not this is an issue in code or in content. Content issues can be fixed "mid-release". Code issues require a Service Pack.

 

We'll try to take a look sooner than later!

Link to comment
  • 4 weeks later...
  • Vectorworks, Inc Employee

So, just an update on this:

 

Just a few lighting devices in Vision leverage a concept called a Lightmap. This is something entirely in the backend and something that is not seen or editable by the end user. Anytime that a Lightmap is present, Vision ignores the Color Temperature field and uses the Lightmap image instead.

 

Part of the issue being reported is that Vision was not making it clear to the end user that this was the case. The Color Temperature was filled out with a value that didn't really make sense and it was editable when it should not have been.

 

The solution is in Vision's code base we need to handle populating the Color Temperature field as read-only when a Lightmap is present. This way, it is clear the field cannot be modified as it will have no effect.

 

So, @DBLD, the solution to your problem is to use a different fixture / fixture mode. If one does not exist that does the Color Temperature stuff you need, you can request it through the Fixture Request form for Vision. I'd have to check with our content team, but in theory, we could provide a molefay that does not use a lightmap and therefore would have an editable Color Temperature field that would allow you to set it to whatever you want.

  • Like 1
Link to comment
  • Vectorworks, Inc Employee

I had a chat with content and realized why things are being done the way they are.

 

The "quickfix", as I stated previously, was to simply disable the Color Temperature field. This was intended to hold us over and allow for a more intuitive UI until we could investigate a real fix.

 

What I'm investigating now is how we can handle both a Lightmap AND a Color Temperature in Vision source code / rendering engine. The Lightmap provides certain effects that content cannot remove without breaking the fixture. So, this must be handled in code. Luckily, the ground work is going pretty well.

 

Whenever there is any update on this, I will do my best to post them here!

 

@DBLD, if you need a "fix" sooner than this, you can kind of hack things up in 2021 to work. I was hoping to avoid posting this, but I hate to leave you hanging. There is a par.png file included with Vision installations. I would back this up before you do anything. But, if you open the par.png in paint / photoshop / gimp and paint the white sections an amber-ish color, you'll get closer to the look you are going for. Please note; this may break other things and may need to be manual "undone" by hand when some of my fixes ship. Perform this "hack" at your own discretion.

Link to comment

Hey Bbudzon

 

Thanks for the update. It is mainly just that fixture that is the issue for me. I don't specifically use the Thomas 4-light molefay but I have found its a good fixture to put in and use in my plots and visualisations. If there was a generic one I would certainly use it.

 

I probably won't do your hack, I don't want to break anything else because when its working its good and time is sometimes of an essence so I don't want to be messing around with something that could get me unstuck later. Most of the time when I am programming a show it isn't a worry, its just when I am producing renders or videos to show to clients that I want it to look realistic.

  • Like 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...