Planetside Software Forums

I encountered this problem today. I tried several times to delete Daniil's shader from the node setup, but every time TG crashed. No matter if I unhooked all masking and disabled it; crash. I had to open in text editor to cut it out.
Anyone else having this problem?

Nope.
But I use only the free version of classic erosion and my test network did not have a lot of nodes.
I can delete it right out of a network, no disabling and/or disconnecting needed.
To be sure I just downloaded it again today and reinstalled.

CHeers, Klaus

I usually can delete it, but not this time. I'm on a frontier version, so I'll do a little test...

If you're using the 4.5 build from the alpha forum, this is something I'm aware of and currently debugging.

Also, please post issues related to builds you download from the alpha section in the alpha section. There are a number of new and experimental things in the v4.5 builds!

Sometimes this just happens. May not be alpha version. Happens to me with DKCE or even just regular shaders. There are times TG won't let me delete the default SSS or fractal terrain without crashing until I do a full reboot.  ::)  Been this way since TG2.

Quote from: WAS on April 13, 2020, 02:32:26 PMSometimes this just happens. May not be alpha version. Happens to me with DKCE or even just regular shaders. There are times TG won't let me delete the default SSS or fractal terrain without crashing until I do a full reboot.  ::)  Been this way since TG2.

Can you provide a scene where this happens, along with steps we can follow to reproduce it?

Ulco's crash is different; it's specific to v4.5 and that one shader.

Good to know, Matt. I was about to send you the file, but that's not necessary I guess. I will post in alpha from now on, but didn't relate it specifically to the latest build. Sorry.

Quote from: Matt on April 13, 2020, 05:07:53 PMCan you provide a scene where this happens, along with steps we can follow to reproduce it?

Like I stated, it's entirely random. Such as loading the default scene shipped with TG and it's default simple shape and fractal terrain shader. It just happens at random. Some sort of conflict in the framework more than anything with the shaders I figured.

Quote from: WAS on April 14, 2020, 03:12:12 AMLike I stated, it's entirely random. Such as loading the default scene shipped with TG and it's default simple shape and fractal terrain shader. It just happens at random. Some sort of conflict in the framework more than anything with the shaders I figured.

I have not been able to reproduce it, so if you can think of anything you might have been doing - or Terragen was doing - when this occurs, let me know. Until then I am working in the dark. You're not rendering an image while deleting nodes, are you?

No, it literally be like, for example starting up TG, fresh default shipped XML, and going to delete the starting shaders to do my own thang' and it just CTD. It's been mentioned a lot in the forums random crashes with deleting nodes or hookin them etc, but like I mentioned, I think it may be the framework itself and Windows. I've gotten so used to it that I just restart when it happens but next time I'll check logs and such, but as far as doing anything, no, nothingg besides deleting nodes in a blank project, or in other instances deleting other nodes, but not rendering or anything, though I have done that in the past, no lie but that's an immediate "Doh" sorta moment where I know why.

Since it will happen over and over regardless of fresh TG process i assume it's gotta be something happening with OS and TG running, and all the TG work overtime, or another process I use interfering.

1) If you start Terragen fresh, and then delete one of those nodes, what percentage of these runs would you say it crashes on the first delete?

2) Does it crash if the 3D Preview has finished rendering before you delete the node?

3) Please try running with the command line switch -no3dpreview (including the dash) and see if that changes the stability.

Question to everyone else: Does anyone else have Terragen crash when deleting nodes? Can we find some commonality among systems where this is happening (e.g. hardware, drivers, Windows version)?

I do, very occasionally, and I think it has to do with the preview being busy, and perhaps after a long session (so a lot of memory used up). I'll keep an eye open for such occurences.

I'll give those suggestions a try. As far as frequency maybe 1/20 (maybe even less frequent, hard judge off top of my head). Not very frequent, but over the years have seen it a lot. I believe I've tried pausing the preview when frustrated with the same crash over and over, however.

Edit: I made a shortcut -no3dpreview, I'll use this mode for awhile and see if it shows.

Thanks.

Quote from: Matt on April 14, 2020, 06:30:18 AMQuestion to everyone else: Does anyone else have Terragen crash when deleting nodes? Can we find some commonality among systems where this is happening (e.g. hardware, drivers, Windows version)?

Since you ask, I sometimes crash when deleting the three very first nodes of a fresh, default TG scene (after the pre-render). Not bothering me the slightest though.

crashable.png

I have adopted a workflow where I am a bit more patient (which is hard) before deleting stuff, and never do that (or change anything but clouds) with RTP on. And actually I should pause the preview or close the field before doing so. But it shouldn't be necessary of course. Though I also don't have the best graphics card, so that may play a role.

Quote from: N-drju on April 15, 2020, 10:24:59 AM

Quote from: Matt on April 14, 2020, 06:30:18 AMQuestion to everyone else: Does anyone else have Terragen crash when deleting nodes? Can we find some commonality among systems where this is happening (e.g. hardware, drivers, Windows version)?

Since you ask, I sometimes crash when deleting the three very first nodes of a fresh, default TG scene (after the pre-render). Not bothering me the slightest though.

crashable.png

I'm glad it doesn't bother you. Restarting my whole system where TG is just one element of my workflow isn't good. Or a good experience for users I'm general. Would be nice to find what it is.

What I do notice is before the crash, sometimes TG hangs, and what you see is the shaders renamed "STRING_" before TG disappears. Makes me think it's not preview related. Perhaps it's the parser checking shader names and positions to rebuild the node network if a shader is deleted.

The string renaming (all shaders) has only occurred to me once last year, when adding a new object. Totally unexpected, but it didn't crash. There must have been some 'same name part' in that object to trigger it.

Hey @Matt is the -no3dpreview flag suppose to disable all 3D previews in TG? In task manager I still get GPU usage on GPU 0

The Node Network uses OpenGL, so that will use the GPU. You can also turn that off with -nonetworkview if you want to try it.

These flags don't completely disable those features. They only stop Terragen from opening them automatically at startup (or when loading a project). You can open those views at any time.

I had to try it now to remind myself, but it doesn't stop all previews from opening. The terrain preview will still be opened at startup, assuming you are using the default scene. To close this you need to switch to a layout that doesn't have anything to preview, such as the Cameras layout.

Ok, thanks. I guess I'll try to disable dynamic layer, close the preview and try from here. Was still getting crashes, but with what you said here it sounds like it could still be same issue we're trying to avoid.

Quote from: WAS on April 21, 2020, 02:56:37 PMOk, thanks. I guess I'll try to disable dynamic layer, close the preview and try from here. Was still getting crashes, but with what you said here it sounds like it could still be same issue we're trying to avoid.

Has this helped?

Yes, actually. From what I can tell, as long as I uncheck dynamic layout, the 3d preview doesn't open, and I am also not crashing. In fact I had the same project open for 3 days working on it extensively (even lazy about it and didn't rename the 60 odd shaders until like day 2).