Renerabbitt

Either/or works

I wont get into detail here but a p-solid and you can edit the layer and components panel accordingly.

I would disagree with who you spoke to at Lumion. Chief really uses decently low poly counts for everything. Your best bet for optimizing is taking it into a 3d optimizer program but even then the reduction will only be a few percent. NOT worth the time at all and 2M polygons is NOTHING for a 2080 TI. And in terms of RAM, your VRAM is what's important here. I run full walkthroughs on a 25M model in Twinmotion using a 1070 GTX. My guess is this, the models you are adding in Lumion are what is slowing things down, or the texture resolution of your material files. Want to speed things up? switch to 1K resolution textures. Really easy to cripple a computer if you're maxing out its VRAM, which happens with 4K+ textures pretty quickly. Also consider phasing your project..all of the top pros do it. I turn off parts of scenes that are not in shot. My layer stack is very organized in Twinmotion for this very reason. Just so you know, Lumion doesn't take advantage of SLI so the second card isn't doing anything in this case.

Tsk tsk for putting “preferences”

I would use shaped landings.

Your answers lie in googling "Section 721.6 "

Would you mind confirming whether or not your 3d connexion device or it's dongle/receiver is plugged into the computer? I mentioned this in your previous thread, there is a known issue with the 3d connexion mouse and plan/elevation views if the connexion mouse is not plugged in. Possibly play around with different USB ports. (not to be mistaken with connexion configs or drivers, this issue is specific to the port and the presence of the hardware) Aside from that I would suggest resetting any GeForce Profiles, or possibly delete and re-establish one for Chief as this has been a known fix for users that may have previously changed some settings in the base profile Cheers

Would suggest the new surface studio laptop over the surface pro. The Surface studio 2 has an outdated graphics card and I would not recommend as it will not support the new PBR RTRT option

Ps 2021 grabs 0/97/125 or 0/96/125 for RGB. Also, luminance numbers are always way wrong in Chief

Where are you “checking mono slab?” You should be checking it in the patios room panel . As opposed to Build Foundation

Hey rob, just a suggestion/request. Mind changing the thread title to something about AMD driver issue crashing etc. Easier to find and reference. Then mark your solution and it will help a lot of folks!

I've posted about this before but this is just funny. Style pallet glitch when the library can't find the original symbol.

You can mull two doors together that have 0" between them.

Ha, are you out here trolling me? I said an apology in the other thread, I don't engage in battles this way, I'm a very friendly and giving guy. Name is Rene Rabbitt, nice to meet you. Back to topic, It specifically is an issue that is occurring by the camera view being rendered causing a Windows Time Out and killing the gfx card driver. My statement was true, could it be solved on CA's end..I'd guess that probably it could...but in the meantime I'd take the steps required to keep moving forward as so many of us have gotten around this issue. Some of these issues pop up if you have custom profiles loaded in GeForce experience. None of these issues thus far have had anything to do with the CPU vendor that I have encountered. I offer Chief training and so have already troubleshooted about 30 machines now, all needing some sort of better handshake between windows update, the gfx driver, and Chief. If people reading this have SSA..call Chief When I was a Beta tester on the early versions of X-13 I ran into this issue frequently with the same error message and it was explained to me by the BETA reporting team that any note regarding the Astral engine and "Device Removed" is in fact a timeout issue with the new Dirctx12 based rendering engine. It occurred 100% of the time on one plan I had until I went into the registry and changed the TDR delay value, which immediately circumvented the issue.(much to my Beta reps dismay) Though subsequent releases of X-13 along with doing a clean driver install and some windows updates helped me revert the reg key back to OOTB. Brian Beck of Chief actually bought my same Surface Book 3 to test out the Quadro gfx card drivers to work through this. Love these guys. As stated in the other thread, I agree that we can hope for some fixes to X-13's code, but in the meantime...why not try some of these things out.

bigger question is why are you at a standstill and reverting back?

Export to dwg and trace or do what Joey said

Solution- ditch the rich text and never look back. Also, you’ve been using the software long enough, maybe time to start using macros for everything? Make global changes in one place. I have a template CAD detail page where I just drop in notes for the type of job I’m on and it populates all of my text notes in all other cad details or elevations

What does that mean, that you can’t open it? is your rowdier window missing? Is the library’s browser tool checked or unchecked? have you reset your side windows from edit/preferences/reset options ?

Something to note for your particular example you posted above. You don't have all of your lights turned on for that camera view. That will greatly increase the possibility of a timeout when in RTRT mode

This is a Windows Graphic timeout issue that coincides with your gfx driver, whatever it may be. Lookup TDR

@plannedRITEand @Kbird1 If clean gfx drivers or updated drivers arent a solve, take a dive into google for TDR fixes. Windows is resetting our gfx drivers after the card becomes unresponsive for a time.

Did you install the latest Chief program update dated the 18th?

This might be a problem with the 1907 and its virtual driver conflicting with the nvidia drivers. Your 1907 is likely using a USB connection? In chief goto preferences/Render/Video Card Status and paste a screenclipping here of what is shown there. I would also unplug your USB monitor, reboot, then fire up chief and see if you have the same problem.

You might consider a separate thread for this as I am pretty certain this is not a mouse issue. I'm guessing the issue is with your 1907FP?