 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
nemesis wrote:
> Chris Cason <del### [at] deletethistoo povrayorg> wrote:
>> I presume no-one had problems with this EXE?
>
> I'd be glad to be of any help, but I'm running Linux.
no problem, there have been a few folks who did download it, and I guess no
news is good news :/
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> I presume no-one had problems with this EXE?
I'm probably too late but I just found the Tools menu empty and couldn't get
"reloaded" until I moved the pvtools.ini to the location being asked for.
Here's what the messages said, before and after:
Loaded 0 tools from C:\Users\Bob\AppData\Roaming\POV-Ray for Windows\pvtools.ini
into Tool Menu.
Loaded 8 tools from C:\Users\Bob\AppData\Roaming\POV-Ray for Windows\pvtools.ini
into Tool Menu.
So I'm not sure if this was a problem or something unfinished or...?
I did the pvengine /install from a command line and that seemed to do what was
intended. Have the 3.7 registry entries. What I had done was to create a
duplicate folder renamed POV-Ray for Windows v3.7, containing everything from
the v3.6 folder.
Also renamed the help file as suggested and it works, too.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Sorry, I neglected to give system info:
Vista Home Premium
AMD Turion 64 X2
And just now realized the SSE2 does crash when drag'n'drop is done. Error is
access violation exception generated at address 0x0060b9d4
Regular pvengine.exe doesn't crash.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
sorry again, not thinking!
That SSE2 wasn't part of this beta 25a, so of course you already knew that. I
wasn't paying attention to what all I copied over to the new v3.7 folder I
made.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 11 Feb 2008 02:18:57 +0100, Chris Cason
<del### [at] deletethistoopovrayorg> wrote:
> I presume no-one had problems with this EXE?
I did a fresh install of 3.6.1c, verified that it works, and then tried
the beta exe:
When launched from a subdirectory of \POV-Ray\bin, I get "ERROR: Cannot
find Home entry in registry (and cannot infer it)."
When launched from the \POV-Ray\bin directory, I get an access violation
exception.
The machine in question is running a Core2Duo E6600 (2.4 GHz) with 2 GB
RAM on WinXP Pro.
--
FE
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Fredrik Eriksson wrote:
> When launched from the \POV-Ray\bin directory, I get an access violation
> exception.
yes, I just found this myself, which is why I put off the source release a
day or so. thanks for the report.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Frederik, Kyle, Tom - you should have received email from me by now with a
link to the source code preview. If not, please check your spam filter.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 13 Feb 2008 10:06:07 +0100, Chris Cason
<del### [at] deletethistoopovrayorg> wrote:
> Frederik
Hmpf!
Some preliminary remarks:
Building the editor dlls requires that you have the ATL libraries and
headers installed. They are included in the default installation options
of VC2k5, but can be deselected. Not a big deal, but worth mentioning in
the build instructions.
Using the 'DEVELOPMENT' macro to make POV-Ray search for the editor dlls
in the 'codemax' directory (as described in the readme) does not work,
because it looks for them in the wrong place. POV-Ray looks for
'"..\\codemax\\" BINDIRNAME "\\" EDITDLLNAME', but it should be
'"..\\..\\codemax\\" BINDIRNAME "\\" EDITDLLNAME'.
The linker fails to link in the debug info in 'vc80.pdb' because it is not
in the same directory as 'povcore-debug.lib' (one is in 'Win32 Debug', the
other in 'bin32'). I have not yet investigated what impact this has on
debugging.
Compilation produced no errors though, and the resulting executable seems
to work fine. I have not attempted to add OpenEXR yet.
--
FE
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris,
I sent you an email reply outlining my results. Let me know if you don't get it.
Kyle
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 13 Feb 2008 22:49:19 +0100, "Fredrik Eriksson" <fe79}--at--{yahoo}--dot--{com>
wrote:
>Building the editor dlls requires that you have the ATL libraries and
>headers installed. They are included in the default installation options
>of VC2k5, but can be deselected. Not a big deal, but worth mentioning in
>the build instructions.
As a side note, the ATL libraries and headers are not included in VC++ 2005 Express
Edition. The
header files are in the Windows platform SDK, but the atlthunk.lib library isn't. I
found a
workaround that seems to have worked here...
http://www.codeproject.com/KB/wtl/WTLExpress.aspx
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
