Jump to content

tdebicki

Member
  • Posts

    7
  • Joined

  • Last visited

Posts posted by tdebicki

  1. I've recently worked with a couple of extremely steep sites and attempted for about 3 days to battle the same weird 3d behaviour: sudden jumps in contours, giant cliffs, holes, sudden peaks, unexpected contour changes in response to adjustments elsewhere and persistent errors while applying numerous modifiers at once...

     

    I stopped and researched the issues... and I found a Design Summit talk by an engineer (DTM team leader?) explaining DTM workings in a technical, but understandable language. Not a riveting presentation, but an enlightening one. This led me to develop a workflow that actually produced the results for me (mostly...), at least for the visual aspects.

     

    Instead of modifying the contours in DTM, I modified them in 2D (converted from 3D source data), deleting the unneeded ones, making new ones, etc... ensuring that they were not exactly one over another. Bringing this back into 3d and then into DTM mostly worked. A rather tedious process, but still better than 3 fruitless days of frustration...

    Placing 3d loci at known locations (buildings grade points, other geodetic elevations) and using them as source data works great for smaller projects, but the modification issues remain - one can't simply cut a hole for a building.

     

    I really wish DTM worked better. It would be far more useful if it allowed 3D points to be placed directly one over another, if one could directly query any point to get full xyz coordinates (this goes for every object we create, OI palette could give project and layer z in addition to xy and area without any extra clicks) and, most importantly, if it could interact with other objects. Instead of attempting to create a pad (useful for the land configuration, but a multi-step process) one could simply place the foundations of the building at the right geodetic elevation if it could simply cut the terrain model to accommodate it. At the moment numerous conversions and exports are needed to be able to at least subtract solids, but then there is no easy way back to DTM...

     

    I realize this transition won't be trivial given the current primacy of 2d data, but I'm just dreaming of a real, full 3D... (or maybe I'm in my covid brain fog...)   

    • Like 1
  2. 7 hours ago, RonMan said:

    It looks like you ran out of virtual memory. I didn't spend much time on the crash dump, but memory is the problem. I could be physical or virtual, but the exception happened when trying to expand virtual memory beyond the allocated memory. 

     

    How much memory do you have on your system and in your GPU?

    Thank you, RonMan!

    That's a thought! I'll go tweaking! I'll increase the limit on virtual memory, but I wonder how it could run out of memory, while I have 32Gb, optimize it regularly and never use more than 75% of it... It was closer to 50% while I worked on this file... 

     

    I'll also try to replace imported symbols, move the origin (I'll make a new drawing and just keep a loci on the current origin, to return to it before exporting - not sure how this will work)... I'm not very optimistic, I suspect the fix will have to come from Apple and VWx... but let's keep trying 🙂

     

    GPU is Radeon Pro 580X 8Gb ... there must be a way to check how it's working, I can do it on PC...

  3. On 3/18/2020 at 7:06 PM, DMcD said:

     

    2018 was pretty solid. Sure there were feature limitations which largely still exist in 2020 but it did run reliably. 

     

    •• Only two crashes yesterday and one was VW leaving the room while it was in the background. Probably only 15 minutes lost reconstructing files from backups.

     

    D

    Congrats on only 2 crashes! 

    I just had another darn crash, so I copied the automatically generated report and I'm posting it here. 

    I opened an older version of my file (1 week old) and wanted to test the plan shadows on it. Crashed as soon as I hit OK on class settings... the file is barely over 50Mb... 

    I'm switching to PC tomorrow (everyone is at home due to the bloody virus, so I can use any one of my machines... lucky? not so sure in these circumstances...)

    Automatic crash report.rtf

  4. On 3/10/2020 at 3:54 AM, shorter said:

    Does this happen from the outset ie when creating a brand new file and copying a group?

     

    is the view rotated when you copy?

     

    is the data far from absolute 0,0?

     

    does the file contain scaled symbols?

     

    are you using PS?

     

    are you using design layer viewports?

     

    does the file contain legacy DWG import data eg line styles, hatches, symbols?

     

    how large is the file or does it not matter?

     

    which version was the file originally created in and has it been converted to 2020? Check by opening a copy of the file using TextEdit.

    DMcD describes exactly the same problems I'm having with VWx 2020 on loaded i9 MacBook 16" and i9 iMac, both w/32GB Ram and upgraded cards running two monitors.... I have crashes every hour or so, my autobackup is set for 7min so I don't lose too much work.

    From the list above, I observe crashes with:

    - rotated plan (quite a bit)

    - data far from absolute 0,0 (I'm working on a large urban design project with many collaborators)

    - scaled symbols (coming from other consultants)

     

    My file is typically under 250Mb, which shouldn't be a problem for the RAM and VRAM to handle, I'd think. But even saving and reverting to saved doesn't seem to help for long. 

    I clean all caches, do a safe boot and then reboot again after every crash or two, this seems to make no difference, neither does purging, compressing images, etc... The file has been made (and remade a few times through both: layer import reference and/or copy and paste) entirely in 2020 version. 

     

    We also run an i9 PC with Nvidia 2080, I haven't tried the file on it yet, should I? Any help would be precious as I'm fighting against a deadline...

     

    Independently, I seem to have some snapping problems (they were there since MC times, but seemed to have been largely addressed before), but I assume it must be the issue of re-setting the key preferences again....

×
×
  • Create New...