Started by jlipstock, July 03, 2019, 06:58:55 pm
Quote from: Matt on July 05, 2019, 05:29:43 amThe -cropoutput command line option uses less memory for cropped renders, so this is worth trying. But it's not just for command line rendering. You can use it with the GUI. If you go to a command line window or console window and run Terragen with -cropoutput somewhere in the command line, you can use the full GUI as normal. Or create a shortcut with this added to the command line options.
Quote from: Oshyan on July 04, 2019, 09:18:27 pmBtw Danny, Defer Atmo doesn't really use more memory to render for equivalent quality levels. At least not in my tests. It does sometimes take longer to render vs. without, but the situations where that's true are fewer and fewer, especially with v3 clouds, and as the renderer has been optimized further since Defer Atmo's introduction.- Oshyan
Quote from: D.A. Bentley on July 19, 2019, 04:03:47 pmI would like to add to this discussion with a related point but not exactly the same thing, but it's important to know about it. Sometimes Terragen will appear to be finishing a render, or it might have already finished and POOF it goes waay (crash). When this happens to me it's not a memory issue because I have 128GB and never see my memory going much over 64GB of use. What I suspect is because I don't always pause the RTP it will start back up after my renders finish, and if RTP runs into a bug somewhere while refining it could cause a crash. I suspect this because I do get my render frames saved, but when I come back to my PC and check Terragen is not running. Of course I get scared, and check to see if my frames were saved and they were. So even if Terragen crashes, always check to see if your frames were saved.There is also an option in Preferences (File Saving) to save all renders even if you don't chose "Render All to Disk" or "Render sequence" from the Render Panel.-Derek
Quote from: Application LogsFault bucket 1935929454206262490, type 5Event Name: FaultTolerantHeapResponse: Not availableCab Id: 0Problem signature:P1: tgd.exeP2: 184.108.40.206P3: 5C563A10P4: ffffbaadP5: P6: P7: P8: P9: P10: Attached files:\\?\C:\Windows\SERVIC~3\LOCALS~1\AppData\Local\Temp\FTHA2F3.tmp\fthempty.txt\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA333.tmp.WERInternalMetadata.xml\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA538.tmp.xml\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA545.tmp.csv\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA585.tmp.txtThese files may be available here:Analysis symbol: Rechecking for solution: 0Report Id: 2e173674-475e-4460-854b-da1b75244bffReport Status: 268435456Hashed bucket: 29ddb3a5f5c64a6e4addcd94e42e1cdaCab Guid: 0
Quote from: Application LogsFaulting application name: tgd.exe, version: 220.127.116.11, time stamp: 0x5c563a10Faulting module name: ntdll.dll, version: 10.0.17134.799, time stamp: 0x7f828745Exception code: 0xc0000374Fault offset: 0x00000000000f479bFaulting process id: 0x2a68Faulting application start time: 0x01d53dc5fc21846aFaulting application path: C:\Program Files\Planetside Software\Terragen 4\tgd.exeFaulting module path: C:\Windows\SYSTEM32\ntdll.dllReport Id: a7ea3a24-a2bb-4291-81b9-eb554818c2cfFaulting package full name: Faulting package-relative application ID: