Therm 7.8.16 Snaps and Draw / edit points functions not working

[Steve]

Hello, I'm having trouble accurately drawing over an dxf overlay.  The dxf file lines are on layer 0, but are not polygons but single lines.  I'm using different combinations of snap to overlay, vertical, horiizontal smart snaps, snap to angle.  My model has several gaps between polygons that I didn't discover until the work is almost complete.  The snap function seems very buggy and I find the line sometimes snaps to the end of a line, but sometimes snaps somewhere along the line or not on the line at all.  The only way I have confidence in the accuracy is to zoom to maximum which is very time consuming.  On circles I drew the polygons on 15 degree angle snap.  Is this too tight?

I'm trying to correct the polygons points, using the "move points" tool and it doesn't function per the manual instructions.  It very difficult to have the two overlapping arrows to display and when it does it rarely works.  When it does work, it want to keep the line moving parallel to the original location instead of allowing me to drag a single point.  

I have an older reference model created in a prior version of therm and the "move points" tool works normal in 7.8.16.  I checked the preferences on both files and they are identical.  The main difference between the two files is the circular polygons are drawn with fewer segments.  

[Robin Mitchell]

There is a lot of discussion on the forum about DXF files. 

You might take a look at this one which explains how to save the DXF file so that you can use autoconvert. 

https://groups.google.com/g/lbnl-therm/c/8w6YuDIECMY/m/8mW61RTbAwAJ

Saving as closed polylines might also help with the snap functionality. You can press the "spacebar" to snap the cursor to the nearest point. 

[Steve]

Any comment on why the edit points function doesn't work.  After I press the "move points" button, only the double overlapping arrow appears (four arrows total).  It rare for the non-overlapping arrow (two arrows total) to appear to allow me to stretch a point by itself or delete a point.  The few times the correct arrows appear, it will not allow me to modify the single point of the polygon.  The function strongly started working once after cleaning up some bad points, but I'm starting a new file, and it not working again. 

[Steve]

I just install the program on my PC instead of running windows from my Mac.  It seems like some of the issues are related from using windows on a Mac.   I post an update once I've had more time to experiment.  

[Steve]

The issue is 100% related to using Windows 10 running over parallels on a Mac.  It would be great if there is a bug fix if possible. 

[Robin Mitchell]

What emulation software are you running? The people I know who run THERM on a Mac are using Parallels.

Robin 

--
You can view the THERM forum online at:
https://groups.google.com/g/LBNL-THERM
---
You received this message because you are subscribed to the Google Groups "THERM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to LBNL-THERM+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/LBNL-THERM/973a6064-c415-4723-b398-b88713fb55e8n%40googlegroups.com.

--

Robin Mitchell

Building Technology and Urban Systems Division
Energy Technologies Area
Lawrence Berkeley National Laboratory

[Steve]

Parallels - Windows 10 Pro, Big Sur 11.6.2...Therm 7.8.16.  Is it possible it is a hardware problem?  The strange thing is, the edit point command wasn't working on the Mac, on my file, but on a different file it worked.  After doing something to the file I originally had a problem with, out of no where the edit point command started to work normal.  I started a new file, it wouldn't' work on the Mac.  I took the exact same file, and it worked flawlessly on the PC.  

[Steve]

Uninstalling the program and reinstalling the program appeared to correct the issue.  I had the same issue occur on my pc, where the snap function stoped working.  Removal and Reinstallation also corrected that error on the PC as well.