Jump to content

benkrall.art

Member
  • Posts

    5
  • Joined

Reputation

0 Neutral

Personal Information

  • Location
    United States

Recent Profile Visitors

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

  1. It seems like from your error message, it might be having trouble with the DWG import/export component 👆 I would probably attempt to remove the DWG/DXF folders in the 2025 folder, to see if the software will run once the DWG/DXF components are not found. I do agree it's strange A:\ is listed in the error, it seems like VW may be doing something unconventional here or else the error is not correctly recording where the actual VW files are located.
  2. Hi, I did not attempt to download the 2.0 updater and force the 2.0 install. It just seemed like an uncertain step when I didn't think I would be able to get it working. My understanding from VW support was that since my CAD system is on macOS 13 (which is supported) there might be some specific tech issue with the Redshift components coming in 2025. It is strange because Redshift does work in 2024 - I am just having trouble migrating the project approach since I have to re-light the model to work with how Redshift measures lights differently from Renderworks. Overall there are probably various reasons why 2025 is crashing on people during the splash screen, but removing the files in the application folder does seem like a way to troubleshoot individual components if you need to get 2025 to run. In other words those problems are likely to manifest at the splash screen because that is when VW is loading all the components in the app folder. So if it's crashing hard in some kind of hardware way with a GPU or graphics error, removing the Redshift files or removing the entire cineware folder (disables Renderworks entirely - it can be re-created or dragged back in once you have tested this) would be a possible direction to investigate. Thanks again and credit is due to VW and Domas for at least being able to get my 2025 working even if I can't use Redshift for testing in 2025. it's nice to know it's possible to understand some of these problems and some folks at VW do know how to dig into this stuff. I'll also give credit that I was able to speak to a human at VW pretty quickly - but I was linked to the Service Select phone number, so not sure if customers in other locations like Australia will have similar results. This was significantly faster and a better support experience than I have received in the past, which has always been more of a "wow that's weird dude" response rather than any direction or idea how to attack the problem. BK
  3. I was able to get help from DOMAS at Vectorworks. VW know that this is happening and Domas was able to tell me there is a known bug in Redshift that causes this crash and causes the vectorworks software to be unusable. By deleting the Redshift files shown in the attached screenshot, Redshift can be removed from 2025 and then the software will work. But you will not have the hyped Redshift technology for rendering and so you must disable part of the software you're paying for in order for the software to start. Overall this is really low effort on the part of Vectorworks - they could easily have posted this info the in this exact thread or made any kind of public post regarding this deal breaking bug. So Domas did an amazing job of customer support but overall the company is still horrible on support and quality control. I am not sure what they think people need to do with the software, if they know about these breaking bugs, and do not publicize any solutions and just depend on their customers to staff the support forum and divine the solutions to these tech problems. Super disappointing but consistent with my experience with VW customer support going back many years. So it's possible to use 2025 now, but not with redshift which is the entire reason I was beta testing 2025 in the first place, since redshift is not usable in 2024.
  4. Posting to add that the update tool also does not work, so if you are troubleshooting this pro bono for Vectorworks, updating the software cannot be a solution
  5. This also happens on MacOS. We literally cannot run the software we paid for, it didn't even work for one second after installation. Typically garbage quality control from Vectorworks, and just relying on forum contributions to troubleshoot the software they charge us for every day. Have you tried ... I dunno, turning it off and back on again?
×
×
  • Create New...