Jump to content

Mark Aceto

Member
  • Posts

    4,051
  • Joined

Reputation

2,227 Spectacular

Personal Information

  • Occupation
    Technical Director
  • Location
    United States

Recent Profile Visitors

18,152 profile views
  1. onto my 3rd mouse, a WLMOUSE Beast X Max, and it's still happening, so this is definitely a VW bug (not a unique hardware issue) been slammed, so i'll submit a VB this weekend or next week
  2. Been having this issue for the past 2 weeks while I'm working onsite with my Razer DAV3, so it's not just the Finalmouse ULX. It's absolutely driving me crazy, so I'll submit a bug report with a screen recording when I'm back home next week. Not for nothing, my WFH setup is a MBP in clamshell mode but I also have a desktop PC, so I'll test that too.
  3. unchecking "Save VGM graphics cache" has reduced file size by 60% for me i've had similar 1.3gb files drop to 500mb after unchecking it (it really just depends though, so your mileage may vary)
  4. Common triggers (sometimes but not always), I've noticed so far: Switching to a new Design Layer Changing Design Layer Options (Active Only, etc.) Switching to a new workspace Changing attributes: line thickness I'll continue updating this until I submit a bug report. BTW I just discovered a great workflow for tracking bugs. Hit "Undo" and then "Redo" whenever it happens (as long as it's not a crash). Maybe that was obvious? 😅
  5. in the meantime, keep an install of VW 2021 in case it's not clear above, perimeter mapping appears to be fully functional in VW 2025 if you open a VW 2021 file that has an object with perimeter mapping note: the offset in my screenshot above is the border/bleed on the oversized substrate (if the object had been the same width as the texture, i would not have had to check a single box or edit the OIP render tab settings at all; simply perfect workflow from the moment i assigned the texture)
  6. ok so not only did that work but... i'm almost afraid to share this because i don't want it to be taken away... especially because it seems like restoring that regression would be the easiest lift of all time... here's the workaround:
  7. just tried all of that, and got essentially the same result the filleted surface seems to be another plane as far as VW 2025 is concerned that said, this is a more accurate model (wrapping around truss chords in real life), so now i'm installing 2021 with the hope that i can magically pull this off...
  8. doesn't matter for the study i'm sharing in public regardless of how large the texture is, VW treats the single object at 6 objects, and applies the same texture 6 times (will not map the same texture across more than 1 surface) the actual texture i'm using is the real world dims, and i see 6 instances mapped to this object... for further context, i know i can fake the "design intent" with texture mapping but i'm using VW as i always do to for large format printed graphics to send the shops a build drawing with seams, grommets, image... along with the actual art file (that i use to create the texture in VW)
  9. trying to figure out how to map a single texture across a single object with multiple planes (surfaces) for context, this is a 12' roll of vinyl that will get printed (large format graphics) and hung from / wrapped around a truss structure (you can see how the vinyl material will wrap around the truss towers at either end) whether it's a shell, solid, soft goods border... i can't get VW to stop repeating the image on each plane even though the unwrapped UV surface is a simple rectangle the texture below is a placeholder to illustrate what's wrong (for NDA reasons, i can't show the actual texture which is basically a 40' wide movie poster):
  10. BTW for anyone following this that isn't experiencing the "lag", note in the screen recording that the mouse cursor (pointer) is moving around without any lag. Keep an eye on the VW cursor (crosshairs) that's slowly drifting across the screen independently at the same time. The best way I can describe it is I have to watch the VW cursor "catch up" to the mouse cursor. It starts off somewhere else, and then moves at a glacial pace across the screen to eventually meet the mouse cursor.
  11. Impressed you got a screen recording of this! I haven’t been able to make heads or tails of what triggers this behavior but I have the same issue with my Finalmouse ULX. Not sure if my Razor DAV3 pro does it too (lives in my backpack for onsite work). I’m on macOS 15.4 but it’s been an issue for awhile. Here’s the thing: this only happens with VW. I would love to submit a bug report but I need to be able to reproduce it (other than randomly), so I’ll test the triggers you mentioned above.
  12. Save as Default button--thank you!
×
×
  • Create New...