JMR

Like this, screenshots from a phone video. The black "curtain" travels down the screen a few times before crash. Both different Intel and AMD machines and Win 10/11 OS's. This is a bit rarer than the sudden exit crash, though.

We are experiencing a strange "black curtain" also that slides down the screens and precedes a crash. This is a separate issue from the sudden speedy exit, I think. Again, across completely differenct setups and Win 10/11. VW version 2023, SP8s.

Not sure if this is related, but after doing graphic legend annotations the program stops to think for a loooooong time, after eg. moving something in the annotation space.

Yes, with 2023. The projects are native 2023.

We are experiencing these sudden crashes a lot, too. Worksheets seem to be the usual culprit, but also while drawing something (no pattern detected there). It happens in a blink of an eye, the program simply gone from screen. Across all different pc's and in both Windows 10 and 11. Across brand new machines and very old ones.

Well that does work, sort of! If I set line thickness to .5mm in the attributes palette, the cross looks like a plus sign: No leader line though like you say. Thank you!

Happy new year to everyone. Is there a way to display the stake object elevation so that there is only a plus sign followed by the elevation value? I can't get rid of the dash: Displaying the dash is not an option due to regulations. Thanks.

Option to choose colourful or b/w icons? Or some "Icon styles" settings... Personally find the new b/w ones much, much more difficult to decipher.

Thanks Matt, and sorry for the delay in answering. There is a worksheet function =ANGLE('ENERGOS') which I thought would return the orientation of the element in relation to project north. However, it stubbornly returns North-90 (Vertical 90) for all windows and doors, regardless of which way they are pointing: It seems that the Energos dialog window is the only place this orientation can be set, manually. I haven't found any "north setting" that would have an effect on these. In Document Settings / Georeferencing settings true north can be set, but it has no effect on these values, neither does any heliodon on a design layer. Perhaps I am missing something here...or is it not possible to query the orientation of an object in relation to true north? I would need this information for an energy consultant, they sum up the areas of windows and doors facing different bearings and use this data in determining the energy efficiency of the building. I did a workaround with custom data; gave all windows a special record with a pop-up menu of orientations; then used data visualisation to check this and finally pulled a worksheed based on these - problem solved, kind of. I guess one could query the rotation of the object and add/deduct this from known true north and thereby determine the orientation. I assumed that it would be possible to query the orientation into energos automatically, and also into a worksheet, but it seems I was mistaken. Thanks

Hi all, I need a list of windows/doors and their orientations for specialist energy consultation. I see I can manually set windows and door orientations in Energos project settings, but this is too laborous for a large project. Is there a way to get this information automatically, to a worksheet? Thanks.

As to VW 2024 project sharing, is it still recommended to create a new working file every day as described before in this thread? Thanks.

Thanks! I'm getting close but still get these white lines on the edges - even though both colours are set to black (for testing purposes). The same happens with any selected line and shadow color. BTW the shadows are not transparent...the viewport can be pasted as bitmap thus opening access to the transparency controls.

"Artistic render works - line and shadow" - where can this style be found? Can't find it in my resource manager libraries... Also tried the shadow catcher method but get really weird results (see below). The sample file works fine though, but can't figure out what is different in the settings.

Yes, if the core component was different than the other core component, the walls wouldn't join properly, just like in the first image in this thread. I didn't try with no core specified.

As of 2023 SP4 wall joins regarding this situation seem to work fine, although component join operations are needed to clean up some lines: The core component type doesn't seem to have any negative effect any longer. 1243255895_Walljointest.vwx