Author Topic: Render View close and reopen change to Alpha Channel bug  (Read 912 times)

Offline D.A. Bentley

  • Member
  • *
  • Posts: 234
    • D.A. Bentley
Render View close and reopen change to Alpha Channel bug
« on: November 23, 2017, 08:18:44 AM »
I think I discovered a bug in Terragen 4.1.17 that can be repeated/reproduced.  The steps to reproduce are as follows:

1.  Open Terragen
2.  Render the default scene
3.  Close the Render View (frame buffer window)
4.  Reopen the Render View from menu View -> Render
5.  Switch to Alpha Channel (channels button only available after adding registration / key file)

Terragen crashes.

I just installed Terragen 4.1.18 and the same steps produce the crash.

Out of curiosity I opened up Terragen 3.4.00.0 and get the same crash.

Lastly, I tested this on a 2nd Windows 10 PC to be sure it wasn't specific to one computer, and the crash still occurred.

Hope that helps!

Derek

Offline KlausK

  • Member
  • *
  • Posts: 434
  • Land ho!
Re: Render View close and reopen change to Alpha Channel bug
« Reply #1 on: November 23, 2017, 10:45:02 AM »
Cannot confirm.
Tried and tested on 3 PCs with Windows 7. No crashes here.
Cheers, Klaus

ps: Terragen 4.1.17 and 4.1.18
/ ASUS WS Mainboard / Dual XEON E5-2640v3 / 64GB RAM / NVIDIA GeForce GTX 780 / Win7 Ultimate

Offline D.A. Bentley

  • Member
  • *
  • Posts: 234
    • D.A. Bentley
Re: Render View close and reopen change to Alpha Channel bug
« Reply #2 on: November 23, 2017, 03:10:34 PM »
Thats strange.  I just tried it on my Windows 7 PC and got the same crashing behavior.

Just out of curiosity are you running AMD or Nvidia video cards in your PC's?  All of mine have Nvidia GTX cards.

Offline jaf

  • Member
  • *
  • Posts: 752
Re: Render View close and reopen change to Alpha Channel bug
« Reply #3 on: November 23, 2017, 03:44:03 PM »
I also get the crash (Nvidia.)

Unhandled exception at 0x00007FF94BBEE6E3 (tglib.dll) in tgd.exe: 0xC000041D: An unhandled exception was encountered during a user callback. occurred
(05Aug18) Ryzen 1800x, 960 EVO 500GB NVME-M.2 SSD, Corsair Vengeance 64GB DDR4 3200 Mem,  EVGA GeForce GTX 1080 Ti FTW3 Graphics 399.07 (30Aug18), Win 10 Pro x64, Terragen 4.2.10

Offline KlausK

  • Member
  • *
  • Posts: 434
  • Land ho!
Re: Render View close and reopen change to Alpha Channel bug
« Reply #4 on: November 23, 2017, 04:08:59 PM »
Meanwhile, it hit me too.
I can reproduce the crash as well :(

Mini Dump says:
An unhandled win32 exception occurred in tgd.exe [5520].
The thread tried to read from or write to a virtual address for which it does not have the appropriate access.

Cheers, Klaus

ps: all Nvidia cards in the PCs
/ ASUS WS Mainboard / Dual XEON E5-2640v3 / 64GB RAM / NVIDIA GeForce GTX 780 / Win7 Ultimate

Offline jaf

  • Member
  • *
  • Posts: 752
Re: Render View close and reopen change to Alpha Channel bug
« Reply #5 on: November 23, 2017, 04:45:10 PM »
.... also, clicking on any of the buttons (RGB, Red, Green, Blue, Alpha) causes the crash.  Saving the render and then closing the render window does not help.
(05Aug18) Ryzen 1800x, 960 EVO 500GB NVME-M.2 SSD, Corsair Vengeance 64GB DDR4 3200 Mem,  EVGA GeForce GTX 1080 Ti FTW3 Graphics 399.07 (30Aug18), Win 10 Pro x64, Terragen 4.2.10

Offline Dune

  • Terragen Alpha Tester (Win)
  • ***
  • Posts: 14446
    • www.ulco-art.nl
Re: Render View close and reopen change to Alpha Channel bug
« Reply #6 on: November 24, 2017, 06:41:32 AM »
Confirmed, 3.7.00.1 too.

Offline D.A. Bentley

  • Member
  • *
  • Posts: 234
    • D.A. Bentley
Re: Render View close and reopen change to Alpha Channel bug
« Reply #7 on: November 24, 2017, 03:05:36 PM »
Thanks for the verifications Terragen People!  I'll send a note to TG Support about this after the holiday.  ;)

Derek

Offline Oshyan

  • Planetside Staff
  • *
  • Posts: 12665
  • Holy snagging ducks!
Re: Render View close and reopen change to Alpha Channel bug
« Reply #8 on: November 24, 2017, 09:02:35 PM »
We read here too, though definitely appreciate formal reports via email. I've already replicated and filed this one in our issue tracker though. :)

- Oshyan