| Poster | Thread |
 roMancer
|  |
Cinema4D under WinUAE+wine - "recoverable alert" (and: Amiga emulation performance poll)
Posted on 6-Sep-2016 10:15:35
| | [ #1 ] |
|
|
 |
Member
 |
Joined: 16-Feb-2010
Posts: 11
From: Unknown | | |
|
| Hi,
I've been using Cinema4D 4.2 under WinUAE 3.3.0 under wine on linux Fedora 19 for quite some time, and it worked fine (incl. Depth-of-field rendering).
Now after updating Fedora to release 22 - wine is now at v1.9.12 - WinUAE (still v3.3.0) had some problems starting up, but most of all Cinema4D now causes errors when using Depth-of-field rendering: it looks as if whenever it's finished rendering a line of the output image, a "recoverable alert" (=yellow-text "guru"-screen) flashes up. Rendering finishes, output image looks fine, but takes far longer than expected.
Any idea where to look for a solution?
Some specific wine-lib or something that might only get involved when activating "Depth-of-field"?
regards,
Ro Last edited by roMancer on 06-Sep-2016 at 10:20 AM.
_________________
http://amigaalive.blogspot.com |
|
| Status: Offline |
|
|
thomas
| |
Re: Cinema4D under WinUAE+wine - "recoverable alert" (and: Amiga emulation performance poll)
Posted on 6-Sep-2016 11:58:36
| | [ #2 ] |
|
|
 |
Super Member
 |
Joined: 28-May-2003
Posts: 1143
From: Germany | | |
|
| @roMancer
A recoverable alert is something your 68k software did, it shouldn't be dependent on the underlying host environment.
For more information you have to tell us the kind of recoverable alert.
The most common recoverable alert is a corrupted memory list, caused by software writing over the end of an allocated memory area. Mungwall can detect such errors and prevent the recoverable alert (instead it writes error messages to the serial port).
As a first step I would increase the stack size of the application.
_________________
Email: thomas-rapp@web.de
Home: thomas-rapp.homepage.t-online.de |
|
| Status: Offline |
|
|
pavlor
| |
Re: Cinema4D under WinUAE+wine - "recoverable alert" (and: Amiga emulation performance poll)
Posted on 6-Sep-2016 15:22:22
| | [ #3 ] |
|
|
 |
Elite Member
 |
Joined: 10-Jul-2005
Posts: 9588
From: Unknown | | |
|
| @roMancer
Did you try older WinUAE binary? There were many changes in 3.3.0 which could cause unexpected results under wine (just guess). |
|
| Status: Offline |
|
|
Templario
 | |
Re: Cinema4D under WinUAE+wine - "recoverable alert" (and: Amiga emulation performance poll)
Posted on 6-Sep-2016 15:27:30
| | [ #4 ] |
|
|
 |
Elite Member
|
Joined: 22-Jun-2004
Posts: 3663
From: Unknown | | |
|
| @roMancer
WinUAE because there is the 64 bit, but the emulation is slow because the 68k cpu now are old to software that we need. |
|
| Status: Offline |
|
|
roMancer
| |
Re: Cinema4D under WinUAE+wine - "recoverable alert" (and: Amiga emulation performance poll)
Posted on 6-Sep-2016 18:36:32
| | [ #5 ] |
|
|
|
Member
|
Joined: 16-Feb-2010
Posts: 11
From: Unknown | | |
|
| aha! I think I've found it:
WinUAE has a setting...
Hardware -> CPU & FPU -> FPU: more compatible
Checking this I don't get "recoverable alerts" anymore, and rendering is faaaast again. 
Looks like Cinema4D hits some "critical" FPU instructions, that wine (through WinUAE) cannot handle without setting the aforementioned option. Or something like this. As I said, the only thing I changed about my Amiga-Emu setup was updating wine.
Whatever. Works for me.
Thanks guys! _________________
http://amigaalive.blogspot.com |
|
| Status: Offline |
|
|
12 crawler(s) on-line.
77 guest(s) on-line.
0 member(s) on-line.
