Jump to content

Nicolas Goutte

Member
  • Posts

    411
  • Joined

  • Last visited

Everything posted by Nicolas Goutte

  1. Could it be that the BatchEncryption Plugin is missing oder otherwise mismatching to the version you use?
  2. Nowadays most serial numbers are without dongle, for example E serial numbers. Therefore the problem that you see does not appear in that case.
  3. @RussU Do you mean quoting like that? I have no problem (Safari on Mac)
  4. I do not think you can have so much control of the UI through the SDK. (However I do not mind if someone comes up with a solution I would not see... or know.)
  5. It is not Linux by itself, it is the case-sensitive file system. You cannot start VW on Mac either, while using a case-sensitive HFS or APFS volume. VW was simply not designed to be very (very) careful about how calling the files in the code. (For example, those are bugs you would not detect on Windows.)
  6. Indeed, that is what I would recommend too: use Python. VS was not meant for handling large files. You could even use the csv module, if your data is organized in columns (be it comma separated, separated by tabs or any similar tabular format that the csv module supports).
  7. Thank you for the feedback. I will try next time to answer to check all display drivers, not only the main ones.
  8. The German VW seems to have it: "RAL Design Demo". (The original American VW does not have it.)
  9. Normally it is the other way round: it is the newly started VW that shuts down the older one (assuming the duplicate dialog is not shown). (That is supposed to be a feature, as you might not have immediate physical access to the other computer to shut down VW.) As for GPU issues, VW tends to crash when 3D mode is switched on... which might be quite late. However reading how you describe the load process, it reminds me of another possibility for a late crashes at startup: a totally wrong serial number, e.g. German VW mit US serial number.
  10. Jim Wilson has once ago meant that the limit was 2 MB. No idea if this limit from 2015 is still valid.
  11. For NVIDIA, see this article: For AMD, I am pretty sure there was a description somewhere in this forum, but I cannot find it right now. 😞 Sorry.
  12. I would check which GPU is used for Vectorworks. Maybe the Windows update has reset (or otherwise changed) the Default-GPU.
  13. OK, thanks, that is what I thought. Because on the wooden side, from what I see, the world is not that simple.
  14. Out of curiosity (as one of the developers taking care of interiorcad's NC-Export): when you tell "quite a few options out there to convert e.g. STEP files into generic CNC files", are you taking about wood CNC machines or metal/plastic ones?
  15. Try: gSDK->SetObjectProperty(objID, kObjXPropPreventWallInsertion, true); (Where ObjID ist the MCObjectHandle.)
  16. As far as I understand, Renderworks uses the CPU, while 2D and OpenGL use the GPU.
  17. And here is the article of Jim Wilson on how to use the NVidia settings (sorry, I have not found at first)
  18. Check the following document. Partially it tells how CPU and GPU are used in VW. On your Windows PC, check the NVidia settings to make extra sure your good GPU (NVidia) is used and not the one of your motherboard.
  19. Even if it is not the post or thread I meant, you may see also
  20. If I remember well, some VW employee (Jim Wilson?) had explained it somewhere in the forum. VW tries to save the file by first saving a new file, renames the old file to the backup file name, then renames the new file to the old file's original name, delete the backup file. So probably the Backup-Files (.bak) were kept, as something went wrong along the line (possibly just VW could not delete the backup file).
  21. I think that at least very difficult to react pragmatically to a crash, as a crash is by definition a situation where a program does not know to do else than to abort its execution. Assuming Windows: as for debugging a crash manually afterwards, well that is possible in your plug-ins if you keep them PDB files (of course you have to generate them, even in Release it is possible and you do not need to ship them to the customer. You indeed need the crash dump from the customer too (see his VW user folder). Of course, as it is your PDB file and the one of VW, you will have probably plenty of Vectorworks.exe+offset entries in the trace stack, but mostly it should not hinder you to fix a bug in your code. (I am quite sure there was a good web page somewhere on MSDN how to debug with a dump file and a PDB file, however I cannot find that web site right now, sorry. It is already a few years back when we had to do it, because we could not reproduce a bug by ourselves.)
  22. I can understand that you have constraints. I have just wanted to stress out what is written in the recommendation. Sure, Jim Wilson would be the expert to answer on such a question but as he is not an employee of VW any more, I would not expect an answer from him (too soon). As for a recommendation, sorry, I cannot give you one. First, I am not an expert, second our company (extragroup GmbH) has a general policy not to give hardware recommendations... so that is even more true for this forum.
  23. Well, the system recommendations for VW 2019 have this sentence in the section "Minimum Hardware Profile" for Intel Iris GPUs (which apparently the 650 is part of): "Some integrated graphics cards such as Intel Iris graphics are acceptable for simple models/drawings, but a dedicated graphics card is preferable."
  24. Have you changed your serial number recently? Otherwise, if it is that urgent, go to your VW user folder and rename it. Try to start VW again. Does it work after that?
  25. It depends on the serial number. The 3rd letter of your serial number must be X to be able to do that. See this article from Jim Wilson:
×
×
  • Create New...