Jump to content

Aristobulous

Member
  • Content count

    47
  • Joined

  • Last visited

Community Reputation

4 Neutral

About Aristobulous

  • Rank
    Greenhorn

Personal Information

  • Location
    Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Aristobulous

    Spotlight Objects not rendering in Section View

    In every other viewport they are working as intended, it's just the section viewport. When I have a spare moment I'm going to create a completely blank file and run a test to see if I can replicate in a fresh file.
  2. Here's an oddity I'm running across. I have a file I'm working on for some client renders, there is a mix of spotlight fixtures and regular visualisation light objects. If I cut a section out from the drawing, in this case a front stage view, using the clip cube it technically works, but in rendering it will not visualise the spotlight fixtures, their lights aren't rendered. It's not a huge deal, I'm just missing a couple of gobo breakups on the furniture and my front wash. My workaround has been to just use Vis Light objects for the stage wash, but is this normal behaviour? I haven't tested this yet in a fresh blank file to see if it's something file specific. I normally don't bother with section cuts but decided to do one this time around and then ran in to this little annoyance. Thoughts?
  3. This is something I would love to see, which would make my life insanely easier and hopefully others. Right now Spotlight fixture objects can only handle a single set of beam/field and candlepower figures, but why can't we put the beam, field, and candlepower values in for a low and high end of a zoom range and then have a slider to move along between them in the OIP? Practically every moving light has a zoom parameter, and conventional zooms and fresnels all have posted values for the narrow and wide extremes. As it is, if I adjust the zoom factor of a fixture but want to take advantage of the light calculators I need to manually do the inverse square math on the candlepower values to find the correct number. Surely the object info pallete can handle this level of math and make dealing with zoom fixtures much easier. Thoughts?
  4. Aristobulous

    Focus Rendering Attention

    What I do is fly around in the design layers bouncing between OpenGL and Fast Renderworks in the walkthrough tool, only looking at small pieces at a time before I page up a viewport and start a full render. Would definitely be on board for an option along the lines of 'focus center of rendering on next mouse click' or something. Also I would just love to be able to put the power of my GPU in to the process and speed the whole thing up.
  5. Has anyone else had the issue of visualisation light objects renaming themselves after being edited? If I have a number of light objects and I've renamed them Front-1, Up-1, Back-1 etc in series, often after right clicking and selecting edit from the visualisation pallete and making some adjustments my names revert back to a default Light-1, Light-2 etc and I lose my organisation? Thoughts?
  6. Aristobulous

    Glow textures

    Awesome, thanks Jim
  7. Aristobulous

    Glow textures

    Is the only way to increase exposure to use a camera object? Or can this also be done in walkthrough as well? That could potentially solve two issues at the same time.
  8. Aristobulous

    Glow textures

    I'll give that a shot and see what the results are compared to what I am doing right now. Right now my glow texture is set to take the object colour, with the glow set to white. This was more for speed, this way I can have one texture to worry about and can quickly assign colours by simply selecting the objects and changing the object fill colour. Right now I have the glow texture set to brightness 400 to get the amount of light I want out of them, but I'm wondering if that is causing the colours to 'bloom' to white.
  9. Aristobulous

    Glow textures

    Does anyone have an explanation or a fix for why the "light" from a glow texture is usually a completely different shade from the fill colour? I have a bunch of LED tubes I'm rendering with a glow texture set to the fill colour of the objects. In OpenGL I set the fills and get a nice selection of blues and purples across the stage, but when I render I basically get two colours, light cyan/blue and magenta. Thoughts? Or do other people run in to this as well?
  10. So here's what I want to be able to do: Build a drawing, drop in some 3d venue geometry and scenery etc, add some visualisation lights, and then fly around in OpenGL and tweak the visualisation lights until I'm somewhat happy, then bounce in and out of fast render to double check everything before final render. Here's what happens: If I go in to OpenGL view and select a group of visualisation light objects in the pallete I can turn them off and on until the cows come home, but I get one time I can right click from the pallete and go to edit the light objects. After that one time that functionality stops working. What then also happens is after a while being able to turn lights on and off stops working and the whole light objects functionality stops completely until I restart the program. The Vis pallete says I am turning lights on and off but in OpenGL and renders nothing changes. Needless to say this is getting very annoying having to restart every five minutes tweaking a file for rendering. Edit: And I also forgot to mention, if I rename Visualisation light objects to more easily find them in the pallete, they will rename themselves back to the Light-# standard after performing an edit on them. Is anyone else running in to a brick wall with working with visualisation lights or is it just me? Alienware 15 R2 i7-6700HQ 2.6Ghz 16 GB Ram NVidia GeForce GTX 970M
  11. Personally I think this should be a standard part of the convert to group command. Only being able to retain either 2d or 3d geometry of a symbol being converted is annoying. This would also fix "insert as group" symbols, as you can lose geometry in a symbol when inserted.
  12. Aristobulous

    Title Block 2018

    Thread created in the Troubleshooting forum, thanks Nikolay.
  13. Aristobulous

    Title Block Manager Bug

    Using the new 2018 Title Block Manager, if you go in and edit the Sheet Number and Sheet Name fields from the Title Block Manager in the File menu, it breaks the link between those fields and the actual sheet name and number. The only way to re-connect them is to delete the title block and re-insert. When the connection is intact you can change these fields in the Sheet settings, or the Title Block Border Settings, but not the Title Block Manager window.
  14. Aristobulous

    Title Block 2018

    Hi Jim, I did find a fix. If you delete the title block and re-drop the block from the Style it reaffirms the link. Attached is an empty file with a title block where the update between Sheet Title and Sheet Number is broken. The fields in the manager should be greyed out or something to indicate that they are linked to a field somewhere and shouldn't be changed. title block example.vwx
  15. Aristobulous

    Title Block 2018

    Hi Jim, I see that is how it is supposed to work, but it looks like the link between the Sheet's title and the Sheet Title field in the Title Block Manager has been broken. The Title Block Manager field is a user editable field, and if you type something in there it breaks that link and there seems to be no way to restore it so that the Sheet Title takes over again. This was an import Title Block from 2017, but if I create a new title block and modify the Sheet Title field it breaks that link and the same result happens. Thoughts?
×