Jump to content

James Russell

Member
  • Posts

    391
  • Joined

  • Last visited

Posts posted by James Russell

  1. Hi all,

     

    So I'm having a little trouble with Spotlight beginnings prior to Braceworks analysis.

     

    Please see image and example file attached.

     

    1702011870_ScreenShot2019-09-19at6_21_17pm.thumb.png.3457bce40d4eb154761925bc074850d2.png

     

    I believe I've made the simplest example I can; 1 x Truss, 2 x 0.5T Hoist, 1 x Lighting Fixture.

     

    When I choose to calculate my system my Hoist Workload seems to give me this error of Suspension Point? I've tried to put house points in, I've tried to make bridles to other points in the roof. It doesn't seem like I can just say these Hoist are allowed 500kg each, my system weighs Truss+Lights (in this case ~40kg), give me the green light and no warnings please. This youtube video ( https://www.yout [DONT EMBEDD PLZ] ube.com/watch?v=RKQ3k78EwR8 ) seems to make the process quite easy however I haven't made a rig which is error free yet.

     

    Does anyone have a guide, video, anything which shows Braceworks from start to finish - particularly for those of us working in Spotlight preparing models for Braceworks calculations? Or let me know what's wrong with my basic example and I'll apply it across my advanced rigs.

     

    Hope you're all well.

     

    J

    Please test me - Braceworks without Braceworks.vwx

  2. 3 hours ago, michaelk said:

    Message( 'X: ',pControlPoint02X,CHR(13), 'Y: ',pControlPoint02YY);

    I'd be interested to know if you're getting a result here - if so what.

     

    Probably also if you could expand it to;

    Message( 'X: ',pControlPoint02X,CHR(13), 'Y: ',pControlPoint02YY, 'Sx: ', Sx, 'Sy: ', Sy);

    Just so you could see if those two values are being put / converted in correctly.

     

    The minor problem I can kinda see coming is once the user moves the "End Here" control point pair there's the potential you'll overwrite that data fresh when you make any other refresh to the POI, in anyway (I could be [probably am] wrong here) - as such you might want to put a comparator, something along the lines of (presuming the reference for control points is 0,0 in this context - syntax will be wrong); 

    If((PControlPoint02X<>0),Sx:=Num2StrF(Rx),'')

     

    Like I said syntax aside that *might* be a thing worth doing.

     

    Someone here surely has dealt with floating control point boxes which aren't by default at the start of a polyline...

     

    J

  3. So.. I got angry at VW. 

     

    =SUBSTRING (to the best of my knowledge) doesn't apply for this case where there is mismatched upper/lowercase characters - which I can accept.

     

    So then I decided to write a script - (with the help of my good friend Dan);

     

    --------- Copy below this line into a script of your choosing with Python ------------

     

    #!/usr/bin/env python3


    def removeFixtureId(v):
        obj = v.WSScript_GetObject()
        
        fixtureId = v.GetRField(obj, 'Lighting Device', 'FixtureID')
        fixtureMode = v.GetRField(obj, 'Lighting Device', 'Fixture Mode')

        # Locate the starting position of the Fixture ID within the Fixture Mode
        fixtureIdPos = fixtureMode.lower().find(fixtureId.lower())

        # If the position is 0 or more then it is present (-1 = not present), so we
        # should remove the Fixture ID from the Fixture Mode
        if fixtureIdPos >= 0:

            # We want to take letters from the end of the Fixture ID onwards
            readFrom = fixtureIdPos + len(fixtureId)
            fixtureMode = fixtureMode[readFrom:]

            # Remove any spaces that might be left over from the left+right
            fixtureMode = fixtureMode.strip()
        
        # Return the processed Fixture Mode
        v.WSScript_SetResStr(fixtureMode)
        return fixtureMode

    # Uncomment the following line to activate this script
    removeFixtureId(vs)

     

    ----------------- Above this line only ----------------

     

    Now's where things get interesting. (see attached)

     

    It looks as though the coding in the Lighting Device is swapping to fields around 'Lighting Device'.'Fixture Mode' and 'Lighting Device'.'Old Fixture Mode'. Calling these independently as column headers we get this .lit result (Dan presumes a key matched pair of the overall fixtures list or similar).

     

    I have to tap out and continue with some real work however I would like the Mode field of the lighting device to populate with the Substring of the real Fixture Mode oneway - as the Num Channels currently does.

     

    Enjoy the read.

     

    J

     

    Screen Shot 2019-09-19 at 1.13.08 pm.png

  4. Hmmm. This doesn't happen for me - just the one Y. Made a second Control Point set and they labelled as expected; 'ControlPoint02X' and 'ControlPoint02Y'

     

    I've just finished battling Control Points for one of my recent scripts. Snippets attached below (where relevant) - I can send you the full script via email if you need to break it apart (few relations would have to be made for forum posting!). But never had to write back to the control points...

     

    ------

     

        cpx,cpy,ctx,cty,control_round        :REAL; {Collection of Control Points}

     

    -----

     

                
                cpx := PControlPoint01X;
                cpy := PControlPoint01Y;
                control_round := PControl_Round;

     

    -----

     

                {Creating the Control Point Box and Text}
            
                IF show_title OR show_descr OR show_cat = TRUE THEN BEGIN
            
                { set the text properties }
                TextSize(10);
                TextRotate(0);
                TextJust(2);
                TextVerticalAlign(1);
                TextOrigin(cpx,cpy);
                
                label_concat:= '';
                IF show_title = TRUE THEN BEGIN
                label_concat:= Concat(label_concat,title_descr,CHR(13));
                end;
                IF show_descr = TRUE THEN BEGIN
                label_concat:= Concat(label_concat,body_descr,CHR(13));
                end;
                IF show_cat = TRUE THEN BEGIN
                label_concat:= Concat(label_concat,category_descr,CHR(13));
                end;
                
                CreateText(label_concat);
                
                cptext := LNewObj;
                
                { get the bounding box of the text }
                GetBBox(LNewObj,t1x,t1y,t2x,t2y);
            
                RRect(t1x-control_round,t1y+control_round,t2x+control_round,t2y-control_round,control_round,control_round);
                HMoveForward(cptext,TRUE);
                {message(Concat(t1x,' ',t1y,' ',t2x,' ',t2y));}
                    END;        

     

    ------

     

     

    It's dirty but seems to work for me and my floating info box.

     

    #SorryNotSorry (bad codes are what I do!)

     

    J

     

    Screen Shot 2019-09-19 at 12.58.24 pm.png

  5. Hi all,

     

    I'm attempting to use =SUBSTRING, a function I've been waiting forever for to help me obtain the MODE of a fixture.

     

    See the screenshot attached for more reference. Ideally I would like the mode data to the right of the string in Column B with the delimiter being the content in Column A.

     

    Therefore I thought I could use something like;

    =SUBSTRING(('Lighting Device'.'Fixture Mode'), ('Lighting Device'.'FixtureID'), 2)

     

    Which I had presumed would give me the string '18ch mode Emissive' in Column C. However I end up with 's'. Even as a single cell with manual strings I seem to only get random characters.

     

    Anyone have a little more light to shed on this?

     

    Cheers,

     

    J

    Screen Shot 2019-09-19 at 10.28.45 am.png

  6. @Jim Wilson thanks for the reply.

     

    I checked their paths, nothing foreign there - a simple Users/Name/Documents structure.

     

    One of them overnight has done a re-installation and the problem is solved. I'll keep you posted should it happen again on this machine and will attempt to get a report for review. More the fact that it's currently a 2 from 7 hit rate is kind of interesting. I don't know if this is isolated to the demo or 2019 overall - I would suspect the former currently.

     

    Cheers,

     

    J

  7. Hi all,

     

    Hope you're enjoying the VW2019 release...(ish).

     

    I'm teaching a series of classes here in the world Down Under. Most of my student get the 30-Day trial in order to partake and then choose their purchase path post-classes.

     

    I currently have two students who mid-way through the day are now unable to save work. Here's a list of interesting things happening;

     

    • Autosaving still works on files they were able to save previously (5 minutes apart - 10 iterations worth as my advised settings)
    • The Save, Command-S and the Save As dialogs don't function, just result in a full program crash instantly.
    • Restarting the computer has no effect. 

     

    It's as though 2-3 hours into the class their computers now refuse to save documents - new or old!

     

    One of them is going to do a re-install tonight although as you can imagine it's incredibly frustrating for them.

     

    Has anyone encountered this in any form? Any ideas of things to try?

     

    They're both using relatively new MacBooks (2016/17) High Sierra - super standard specs.

     

    Let me know!

     

    *Sigh* - J

  8. Hi All,

     

    I have a client currently who enjoy the concept of the Project Sharing features although wish for them to be used in a more global environment, unrestricted to a project file.

     

    They have quite detailed plans of their venues with specific things which should not be moved (diagonal bars, fixed height winch bars, fixed curtains, fixed orchestra pit deads, etc.). Commonly they will send these plans in the .vwx format to either external suppliers or prospective hirers who will send the plans back months later with their proposed changes.

     

    The problem is that often these external users will send back a plan with modification to the specific items above (moving grid pieces to locations which do not exist and/or places which have other obstructions, moving the pit to invalid stopping locations, etc). Often these changes go unnoticed until bump-in periods where conflict occurs as both parties believe they are in the right.

     

    The ideal would be the ability to password lock layers within the file. The ability to lock the 'Grid' layer for example and restricting the editing functionality, yet still allow class switching. Should the user need to move something in this layer they call in, receive the password and the file is logged with a change to that layer (possibly within the project sharing History).

     

    I'm aware we have referenced layers as an option although this has been tried and still required either a) releasing a second reference document or, b) the reference being broken and edited anyway.

     

    @JimWlet me know if I'm missing something here. Otherwise wishlist?

     

    Hope you're all well,

     

    J

  9. Hi All,

     

    I'm going a little crazy and need someone to do this bug test for me, two parts;

     

    Part One

     

    1. Make a truss.
    2. Convert to lighting position.
    3. Using Instrument Insertion place a few lamps onto the truss.
    4. Raise Truss lighting position to 6000mm in Z.
    5. Ensure lights stay on truss from front view.

     

    Part Two

     

    1. Make a Truss.
    2. Convert to lighting position.
    3. Raise Truss lighting position to 6000mm in Z.
    4. Using Instrument Insertion place a few lamps onto the truss.
    5. Ensure lights are hung on truss (mine aren't!)

     

    *Optional extra - try to hang more lights on lighting positions, default insertion is 0mm.

     

    Just let me know if your experience is the same. Especially @JimWdo you get this?

     

    Hope you're all well.

     

    J

  10. Thanks all for the great replies!

     

    @Peter NeufeldI really like this. Surface Array is one of those strange beasts that I often overlook in everyday (or in this case not so everyday) tasks, much like the project tool also.

     

    @Marissa FarrellYou tease, haha! I'll have to put my Marionette hat on and dive back in now... Seriously though cool stuff.

     

    I'll be sure to place a shot from the completed file here at some stage in a few weeks when I get some time to render. I'm mid-way through a script which I started last week prior to this, if it works I'll add it here for future browsing too.

     

    ;) J

  11. Hi all,

     

    Before moving forwards this discussion relates to distribute along path, not duplicate along path.

     

    I have an example project for discussion;

     

    I have 308 unique 3D object (they are giant letters) which are currently in a tidy line (almost as though they were typed out, converted to polygons and then extruded...).

     

    I need to distribute these along a NURBS curve which undulates over some hills. It would be ideal if these remain in the same order they are currently, are evenly spaced and followed the NURBS curve's tangents for orientation.

     

    Thoughts?

     

    Hope you're all well.

     

    J

  12. @Kevin McAllister

    Quote

    the plant line tool seem pretty cool on the surface

    Unintentional puns?

     

    I came to a similar conclusion playing with this tool, although has mixed success creating a new item with (or around it) using the fill polygon creating something extrudable. I have had issues with all modes of corners, I would love to see the generation code for this, I have a feeling it just randomly chooses to make new points random(max line length) from the current path and most probably without creative coding probably won't ever be smart enough to make non-self-intersecting creations.

     

    @michaelk- Maybe collect those beers when I touch base with@JimWand finally organise a demo of our NFT Augmented Reality tracking at these amazing VW events you lucky ducks get, then I'll have an excuse to come over!

     

    +1 to all your points. 

     

    It was not the crazy animation script from years ago. That was the Create Animation... > Orbital Point mode in OpenGL. Although the attached is for you in particular:

    OpenGL Cave Animation.mov

     

    ^ IF YOU'RE SCROLLING LOOK HERE

     

    Created in that mystical plugin (available in Australia by default, do you guy have it too yet?) - Animation works. God can I say if this feature is going to stay as a product valued at $200AUD it needs an upgrade (8 years, no update?). Either that or the source code released so we can finally understand how it exports image files via script and then compiles into a .mov.

     

    @grant_PD- For realism I could not agree more. As you'll see in the video above the purpose of this particular design is for a stage set which has a feature wall that automatically comes forwards and engulfs the stage in a cave. Beautiful render by the way.

     

    @Alan Woodwell- Indeed. In the general educational perspective we're looking at a process based guide on taking a line drawing and converting it to polygon/workable objects, not just this cave reference.

     

     

    PS - Sorry the render is so rough, I spend a long time getting timing right, not a lot on the symbol looks.

  13. All,

     

    One of the things I love about being from the other side of the world from you all is I can ask a question, sleep on it, and for the most part you all bring me overnight answers. Thanks! ;) 

     

    @markdd- My bad! Hopefully this post explains it better!

     

    @Moto2 - Indeed. Trace is the first thing my mind says through years of automation/production pains. But in the interest of education and pushing this program to it's limits I have to go further. <insert Star Trek quotation here :P >

     

    @Kevin McAllister - Now we're talking. I knew you'd enjoy the fur cave.

     

    Tracing the outline as above is my instinct. I'm already quite good at it, and it does improve your pro gaming skills at the same time, but in the interest of science...

     

    Illustrator - This was my conclusion also, and as you'll see below is probably the best resultant. I think I was impatient with the trace breakdown, more explained below. Rad answer though!

     

    @michaelk- I really didn't need to owe you more beers Michael, but since you're here you can earn another.

     

    The Plant Line Tool. Oh my goodness. It's amazing but has one fault for my purposes which is the self-intersection of lines when moving to an extrusion. This leads to a question directed mainly at your knowledge-base but also open to others:

     

    When you have a self intersecting object, such as the example below, is there a fill/correct function that can rectify an object automatically?

     

    OMG The Plant Line Tool.png

     

    As for my current solution:

     

    Most of you have probably jumped straight to the (rough - it's late here ok?) video attached but if you're interested in the steps from the raw .jpeg file to semi-completion until next week;

     

    1. Import .jpeg file to Photoshop.
    2. Using the Magic Wand Selection or similar break each piece into a layer with a fill.
    3. Open the new Photoshop file in Illustrator with all the layers intact.
    4. Select each layer and turn on individually.
    5. Use the Image Trace function to isolate and create a path for your shape (one button click but it's pretty awesome).
    6. Save each of these as a .dwg
    7. Import the files into VW, they'll come in as Symbols by default.
    8. Command/Control + K those bad boys, followed by an ungroup.
    9. Delete all the excess, mainly the background stuff and the self-intersecting fill content (I don't know why it's self intersecting <see my question above>)
    10. The remaining polyline is non-intersecting, fill with a colour and a friendly line style.
    11. Extrude and position, probably in a new file as this one will be filled with junk.
    12. Profit... maybe?

     

    I'll keep you posted if more comes of this project but there sure is some interesting questions coming through. Let me know if you're interested in more of this content!

     

    Stay safe all,

     

    J

    Rotation_of_Cave.mov

  14. Forum, 

     

    It's been a while since my last posts, hopefully you're all well!

     

    In among other things I'm tutoring a series of very creative Post-Graduate students with theatrical backgrounds. One of them came to me with an idea that currently I can't solve, perhaps some of you out there might.

     

    Without a serious amount of tracing we wish to create a structure that looks like this:

    Stacked Layers Example Layout.png

    ... however has the outlines of this:

    Stacked Layers Example.jpg

     

    I've tried several things here - 

    • Trace Bitmap Commands
    • Layered Photoshop Files in Broken Layers
    • Exporting Paths created in Photoshop to Illustrator to then save as .dwg and open in VW. (Self intersecting geometry during extrusion got me but it's the closest yet!)

     

    Now I'm asking for input. How would you approach this and create this series of extrusions?

     

    I've included reference files and a .zip containing the PSD with individual layers available.

     

    Any input welcome!

     

    Stay safe otherwise all.

     

    - J

    Stacked_Layers_Examples_-_PSD_and_JPGs.zip

  15. Kevin,

    I totally agree that exportation has gotten better over these versions, but as Tim suggests it still has flaws evident everywhere.

    Attached are two of the most basic examples I can make and a complex. You can from these see the very foundation of problems.

    The first shows the base of an object missing. The creation of this object in VW consisted of creating a 100mm x 100mm Square, then extruding to 150mm, then choosing to export to .fbx.

    The result seems to be that the base of the object has an inward/upward facing normal, most probably due to the extrusion leaving the planar object and then duplicating surfaces around/above it.

    The second example is a little trickier (not). Draw a cuboid as above Front Elevation, mirror to the right, export to .fbx. The result is a flipped normal on the polar opposite side.

    Onto the more complex (not really but compared to the above).

    The basic bridge shown here in both Vectorworks and then again in Unity (note it is the same result in 3DsMax and Blender).

    The OpenGL in VW appears fine. The exported .fbx is far from it. Several missing surfaces, most caused by mirroring. Some of them occur within solid subtractions, some within solid additions. I find that only 1 in 5 object that I create in Vectorworks with (appox) 3 translations (be it an addition, subtraction, then addition of solids for example) actually translate correctly.

    J

  16. Tim,

    Two cents is infinitely bigger than no cents. :)

    I too had found some of these older topics, but none actually suggest a true plausible fix, particularly should this be everyday routine as it's becoming now throughout my testing and development projects.

    There is functionality in blender to redirect normals from a central point but alas this only works on objects that are purely outward facing.

    I really need each geometric object, as a baseline upon creation, to be generated with its normals facing outwards, from the centre of lowest common root object.

    I've attached an image of the most common form of inverted normals occurring on exported mesh objects. Note this object is a test object, in a test scene exported directly from VW. The cabinets shown are taken from the VW standard library.

    Any other feedback/suggestions most welcome!

  17. MK,

    There's certainly something sinister going on here.

    I can replicate your query, with any line type that involves a replicated geometric object. I also noticed that it alters the wrapping of the individual text items around corners, seemingly short-cutting the corner in a way.

    It doesn't seem to be replicated with dashed styles or normal features.

    I'd say bug but like small ant sized right?

    J

  18. Hey superstars of the VW forums,

    I'm currently working on several random ventures, one of which relies heavily on some exports I'm doing from VW into the .3ds and .fbx formats.

    My query relates to how VW handles rendering and exporting the normals of a surface.

    Most of my current exports come out looking like they are missing half their data. On further inspection it's just that the surfaces are inverted, often facing inwards of the object. Even some of the most basic cubes end up with half the sides facing out and half facing in.

    Have any of you had success with;

    A) Creating Double Normals, so that both sides of an object theoretical planar surfaces are rendered (yes double surface data I know).

    B) Reversing Normals, to face them to the exterior of an object. (To push them outwards of a central point)

    I have tried all the typical formats (.3ds .fbx .dwg .dae) and none of them have export settings relating to this data, nor is there any difference in the outcome.

    Hope you're all well.

    J

  19. I can confirm that this issue is currently still actively happening for a select few of my students.

    It seems that something (unknown) causes a single press of Command + Z to change from a single instance undo to performing the entire undo history.

    The issue is worst than just a potential 50 undo actions. Although the Redo option is available it does nothing. Holding the action causes the menu to flash as though the command is being executed but nothing actually occurs.

    I've had this occur on 3 of 16 student's computers over the last month. All using either VW2016 SP2 or SP3 on MacBook laptops of various ages and specs.

    Once the issue has occurred it seems to lock the Command + Z to always perform this mass undo. Restarting the program has fixed it in the past but it's almost guaranteed to reoccur on the computer later in the lesson seemingly unpredictably.

    I can't as yet replicate the problem on my own machines but I would love to know if anyone has some preventive ideas. I have performed a preferences reset as above on a student's computer two days ago in our previous class and the problem has reoccured today.

    Hope you're all well otherwise.

    J

  20. Michael,

    It's got something to do with the Generic Solid within Symbol 'Leaf Decorative 15A'. It's super weird though.

    If you enter that symbol and replace the solid with anything else the door renders correctly. But I can't seem to analyse the solid, nor break it down into anything else.

    I did notice that if you draw a rectangle the same size as the door and extrude it to the same height, then intersect solids between the Generic Solid and the new Rectangular Prism when you exit the symbol the extra pieces will be gone.

    Like buggery I know why.

    J

×
×
  • Create New...