I have been playing around with Moray 3.1 and it keeps crashing on me.
Sometimes Pov-Ray crashes and sometimes Moray crashes along with
Pov-Ray. I am using the latest build. I seem to have the most trouble
with lens flares, I can create one and render it several times but after
several rendering Pov-Ray crashes. I have also attached a mdl file of
mine which consistently crashes Pov-Ray. Am I doing something wrong?

PS: If you want to use any of the objects, in the attached mdl, or the
entire mdl itself in your own scenes PLEASE email me, don't just take
it.

Post a reply to this message

Attachments:
Download 'alter.mdl.dat' (11 KB)

I've been having a similar problem.  Moray crashes and it says error in mfc20.dll  It
never used
to do this, I don't know why it is now.  Only with the new version.  I dunno...?

Post a reply to this message

Hi Thomas Lake, you recently wrote in moray.win:

> I have been playing around with Moray 3.1 and it keeps crashing on me.
> Sometimes Pov-Ray crashes and sometimes Moray crashes along with
> Pov-Ray. I am using the latest build. 
Hmmm, that's strange. Any pattern to the crashes? I'm not sure what to
make of this.

I'll take a look at the MDL file.

- Lutz
  email : lut### [at] stmuccom
  Web   : http://www.stmuc.com/moray

Post a reply to this message

Thomas Lake wrote:

> I have been playing around with Moray 3.1 and it keeps crashing on me.
> Sometimes Pov-Ray crashes and sometimes Moray crashes along with
> Pov-Ray. I am using the latest build. I seem to have the most trouble
> with lens flares, I can create one and render it several times but after
> several rendering Pov-Ray crashes. I have also attached a mdl file of
> mine which consistently crashes Pov-Ray. Am I doing something wrong?

This is the first time that I have seen POV crash. Your Alter model caused a general
protection
fault in the PVENGINE.EXE I was rendering a 320x240 and it crashed after rendering
about 3%. I
could get this to happen every time. Best as I can tell, it has something to do with
the
grouping of the 3 cups.

--
Daniel Hargreaves
SD Graphics
--
ArchSymb for AutoCAD and IntelliCAD
http://home.att.net/~dkh007/archsymb
CADD Standards
http://home.att.net/~dkh007/caddstd

Post a reply to this message

I'm about to send a "solo" bug report in, but first I thought I'd see if
anyone else had encountered the same problem I did. Here's the sum of
it:
I downloaded both the 3.01 and 3.1 versions to compare the two; 3.01
installed and runs fine, 3.1 does not (latest build, direct via http
stmuc site), however, regardless of install sequence and folder name (I
first tried "Moray31 for Windows" instead of the default without version
number added. I used the uninstall between successive attempts too.
The program simply crashes upon trying to run the program at the OK
button in the splash screen, though I was able to run the credits.
The error message states fault with the MACX4W.DRV file which I found to
be located in "Windows\System" folder (an older one also in the
"Windows\Options\Cabs" folder from OEM setup).
Considering the DLL crash, stated in this thread by Kyle, I wonder if
some updated files are neccessary on our systems for Moray 3.1 to be
run?
Or... is this possibly due to the IE 4.01 (psuedo Win98), since it is
mentioned that only Windows 95 is intended to be the OS. Just guessing.

Kyle wrote:
> 
> I've been having a similar problem.  Moray crashes and it says error in mfc20.dll 
It never used
> to do this, I don't know why it is now.  Only with the new version.  I dunno...?

-- 
 omniVERSE: beyond the universe
  http://members.aol.com/inversez/POVring.htm
=Bob

Post a reply to this message

Attachments:
Download 'us-ascii' (1 KB)

Hi Bob Hughes, you recently wrote in moray.win:

> The error message states fault with the MACX4W.DRV file which I found to
> be located in "Windows\System" folder (an older one also in the
> "Windows\Options\Cabs" folder from OEM setup).
That is the screen driver for an ATI card and I have received more
than a handful of reports from users that are getting this error in
their screen driver (always MACX4W.DRV and always ATI cards).
Apparently the ATI drivers are not all that stable. Most of the users
have fixed this by downloading and installing the latest drivers from
ATIs website.

Also note that Moray V3.0 and V3.1 may not coexist peacefully on one
machine (depends on how much manual configuration you're inclined to
do).

- Lutz
  email : lut### [at] stmuccom
  Web   : http://www.stmuc.com/moray

Post a reply to this message

First let me correct myself (and Lutz) on the driver file mentioned
before: it is MACXW4.DRV not macx4w.drv... alas, no matter.

Much thanks Mr. Kretzschmar!
I did suspect the video but only fleetingly as I didn't really know from
whence the drv hailed from. Forget the bug report then, suffice it to
say I do have the dreaded ATI video on this machine alright. Strange
thing is I got a d/l of newer drivers last summer using IBMs Update
Connector and wouldn't have thought there would be more recent ones to
d/l already. I should know better than that by now :) because I had
heard IBM is slow to keep up to the minute on such things. They say they
want to be sure of compatibility issues, fine by me.
I have a 8 or 9 month newer set of ATI video files direct from the ATI
site now. Moray 3.1 is okay. Except for the odd MorayStart.mdl both 3.01
and 3.1 ask for upon startup of the programs there appears to be no
problem running both together that I've seen yet, but then I just got
going.
I may be doing all this for naught considering I don't exactly use
modelors to do much, if any, POV-Ray stuff. But at least I'm on track
now.
Based upon the new features, etc. maybe I should start using GUI though
;)

P.S. an ironic addition, to *my* story anyway, I stopped mid-writing of
this  message and went downloading to check things out first. I saved
the text I had written to come back after anticipating a restart of the
computer and realized afterward I had used the file name morayati which
reminded me of Moriarti (sp?), the Sherlock Holmes villain.
Tried looking "Moriarti" up in an encyclopedia [1983 Funk & Wagnells],
get this:

Moray >snip< The area was occupied in prehistoric times by the Picts and
suffered from Norse invasions in the 10th and 11th centuries.>snip<

Moray eel was in there too (forgot about that snake-like fish, always
thought of Moray as More Ray condensed), no Sherlock Holmes under the
S's, so much for F&W.

Okay, so I'm getting tired. Bye now.

ATI driver d/l's:
http://support.atitech.ca/drivers/

Lutz Kretzschmar wrote:
> 
> Hi Bob Hughes, you recently wrote in moray.win:
> 
> > The error message states fault with the MACX4W.DRV file which I found to
> > be located in "Windows\System" folder (an older one also in the
> > "Windows\Options\Cabs" folder from OEM setup).

> That is the screen driver for an ATI card and I have received more
> than a handful of reports from users that are getting this error in
> their screen driver (always MACX4W.DRV and always ATI cards).
> Apparently the ATI drivers are not all that stable. Most of the users
> have fixed this by downloading and installing the latest drivers from
> ATIs website.
> 
> Also note that Moray V3.0 and V3.1 may not coexist peacefully on one
> machine (depends on how much manual configuration you're inclined to
> do).
> 
> - Lutz
>   email : lut### [at] stmuccom
>   Web   : http://www.stmuc.com/moray

-- 
 omniVERSE: beyond the universe
  http://members.aol.com/inversez/POVring.htm
=Bob

Post a reply to this message

Attachments:
Download 'us-ascii' (1 KB)

On Fri, 08 Jan 1999 08:28:50 GMT, lut### [at] stmuccom (Lutz Kretzschmar)
wrote:

>That is the screen driver for an ATI card and I have received more
>than a handful of reports from users that are getting this error in
>their screen driver (always MACX4W.DRV and always ATI cards).
>Apparently the ATI drivers are not all that stable. Most of the users
>have fixed this by downloading and installing the latest drivers from
>ATIs website.
>
>Also note that Moray V3.0 and V3.1 may not coexist peacefully on one
>machine (depends on how much manual configuration you're inclined to
>do).
>
>- Lutz
>  email : lut### [at] stmuccom
>  Web   : http://www.stmuc.com/moray

Lutz,
   I have had the same problem -- I have the ATI All-In-Wonder card.
I suspected a problem with the drivers because I was seeing this
problem during the time I spent with Betas 3 & 4 (I believe)

  I downloaded the latest drivers from ATI, but continued to have the
problem -- Moray would crash even before it came up completely.
Strangely though, the problem went almost entirely away with the final
release (not build 4215, but the one before that).   I have had Moray
crash only once since installing POV-Ray 3.1 and Moray build 4215 --
but it did crash that once, so I suspect I still have a problem --
maybe I should go for a different (and simpler) video card.

  But is there any reason you can think of why Moray's use of the card
would cause this bug in the driver to surface and other applications
don't?

   Thanks,

        George Hunt

George Hunt
http://ourworld.compuserve.com/homepages/lightsword
102### [at] compuservecom

Post a reply to this message

Hi George Hunt, you recently wrote in moray.win:

>   But is there any reason you can think of why Moray's use of the card
> would cause this bug in the driver to surface and other applications
> don't?
Nope, no idea. Moray does make use of a lot of bitmap handling code
with direct bitmap access, but unless I were to get hold of an ATI
card, I really couldn't tell. I guess if I had an ATI I could program
a workaround, but without it that's totally impossible.

- Lutz
  email : lut### [at] stmuccom
  Web   : http://www.stmuc.com/moray

Post a reply to this message

<snip>
>thought of Moray as More Ray condensed), no Sherlock Holmes under the
>S's, so much for F&W.
<snip>

Try looking under "H" (for Holmes) instead of "S"...

Matt

Post a reply to this message