7 posts / 0 new
Last post
dirkmittler
Offline
Last seen: 4 years 6 months ago
Joined: 07/02/2013 - 04:09
Problem with Aqsis 1.8.1 .

Hello.

I'm new to this forum, as well as to K-3D. I have v0.8.0.1 installed under Windows 7, 64-bit, but think that now this version is being referred to as 8.0.1 .  I'm happy to say that K-3D at least launches. I also just now installed Aqsis 1.8.1 .

When I choose the default 'RenderMan Engine', its 'Render Engine' property defaults to 'AqsisBundled' .  Like that, it renders the scene just fine. But if I simply change the node property to 'Aqsis', I'm intending to use the external, Aqsis 1.8.1 , but nothing renders. It's probable that I'm just doing something wrong. But how can I get K-3D to use my newly-installed Aqsis 1.8.1 ?  I have added the directory of my external Aqsis .EXE File to my System Path.

Also, when I change the node property back to BundledAqsis, it just starts working again.

Dirk

[Edit] There is a known problem with Aqsis 1.8.x under Windows:

http://community.aqsis.org/2012/04/error-reading-socket-10035.html

Less than half of what they say on any Web site is true. This socket error will prevent the user from doing a batch render-to-file as well, because 'aqsis.exe' insists on opening an instance of 'piqsl.exe' anyway. Further, one issue which neither the Aqsis team, nor the K-3D team seem to have solved, is users running either program in non-administrative mode. Hence, in order even to get the Aqsis demos to compile - those demos try to write files to the system folders in which the software is installed - the user needs to open his console in Administrative Mode.

Does K-3D make the same oversight?

In any case, I don't see where in the K-3D GUI  I'm supposed to specify an output file path, to get a batch render. If you guys could show me how to get that working, I'd be happy to use Aqsis 1.8.1 as my fine-quality renderer, and Aqsis-bundled as my preview...

But for now Aqsis 1.8.x is virtually unusable for me under Windows. Therefore, I have reverted my external Aqsis to v1.6 , maybe temporarily. Yet, I still cannot get K-3D to use it, not even Aqsis v1.6 .  I have tried to create a New RenderManEngine, and to set that one to use Aqsis - but with no luck.

 

Bart Janssens
Offline
Last seen: 1 year 10 months ago
Joined: 12/22/2012 - 11:08
Hi,

Hi,

Yes, I am unable to get Aqsis 1.8.2 to work on Windows as well. The bundled aqsis is actually 1.6, so that may be OK for you? Settings for the render can be found in the Camera node. To render to file, you can use Render->Frame from the menu or click the corresponding button in the camera node properties.

In the help menu, you can choose to open the log window. This will show you the path to temporary directories K-3D creates. Inside these, there is a frame directory that contains an rib file that you can feed manually to aqsis if you want.

Hope this helps!

dirkmittler
Offline
Last seen: 4 years 6 months ago
Joined: 07/02/2013 - 04:09
Problem Identified.

Hello.

I think you put me on the right path here, and that I've identified the problem. BTW I have upgraded my external aqsis version to 1.8.1 again.

Aqsis cannot tolerate absolute pathnames that have backslashes. At first, it was not even able to locate the shadercache it created, because within the .RIB File the shader searchpath had backslashes. Because I cannot control the generation of .RIB Files by K-3D, I edited the ' aqsisrc ' file like so:

 

Option "defaultsearchpath" "string shader" ["C:/Apps/Aqsis/shaders/displacement:C:/Apps/Aqsis/shaders/imager:C:/Apps/Aqsis/shaders/light:C:/Apps/Aqsis/shaders/surface:C:/Apps/Aqsis/shaders/volume:C:/Users/Dirk/AppData/Roaming/.k3d/shadercache"]

 

This puts the shadercache in my home directory into the view of the aqsis executable, in spite of the failure to do so by K-3D. But then the next problem which crops up, is that such backslashes are not allowed in the command-lines either. Thus, the external Aqsis fails to compile shaders, so that shader versions are often Aqsis 1.6 shader versions. Aqsis 1.8 again requires compiled shader .SLX Files, version 2. The version 1 files were left by BundledAqsis. Next, it cannot execute the aqsis command-line, even if I feed it the correct shader versions, because again they're specified by global pathnames. Thus, just to type in

 

aqsis world.rib

 

works by now, from the command console in the temp folder, but not so when K-3D tries it.

I imagine that the bundled version of Aqsis just happens to work, because everything there has been put into relative pathnames.

 

Dirk

 

dirkmittler
Offline
Last seen: 4 years 6 months ago
Joined: 07/02/2013 - 04:09
Solved: Works like a charm ! {:-)}

First of all, my earlier explanation was not the definitive answer. I saw that the .RIB File was not being parsed correctly, and had corrected that in the ' aqsisrc ' File, belonging to the external Aqsis renderer.

There was a tiny little detail which had escaped my notice, every time I looked at that Log Window - and yet it was there. My System PATH variable did not have K-3D's /bin directory in it, because it wasn't supposed to. It had Aqsis v1.8.1 as its last entry. But every time ' k3d-renderjob ' ran, it prepended the K-3D /bin directory to the System PATH. And what that means is that when the executable is run, this modified Path gets scanned in the order given.

And so K-3D was always handing the job to the aqsis .EXE File that was bundled, because that was the first place to find it in the modified PATH.

My solution was to rename the aqsis , aqsl , and piqsl .EXE FIles under K-3D's /bin to *.bak .  That's all, that's it. First of all, when I create a RenderMan Engine instance now, it knows not to default to BundledAqsis, and secondly the external Aqsis runs fine.

I just have to remember not to ask for a preview, because of the bug in 1.8.x that was mentioned at the top of my thread. I must always ask for a still frame. If I ask for a preview, then the aqsis.exe process will continue running but without results.

Dirk

 

Bart Janssens
Offline
Last seen: 1 year 10 months ago
Joined: 12/22/2012 - 11:08
Aha! Good to hear you got it

Aha! Good to hear you got it working! I think for future releases (whenever that may be) I will stop bundling Aqsis, it seems more logical to just use what people prefer to install.

Also, just wanted to mention, if you like K-3D, the easiest way to get a more recent version would be to build the latest from git on linux. I just haven't gotten round yet to catch up with the binary releases.

dirkmittler
Offline
Last seen: 4 years 6 months ago
Joined: 07/02/2013 - 04:09
On my Linux boxes, I do a lot

On my Linux boxes, I do a lot of custom compiles. But this goes hand-in-hand with the fact that those Linux boxes (of mine) are very old releases of Debian, such as ' Debian / Lenny ' (You're probably laughing at that). Hence, I can build K-3D v0.7 as a custom-compile, while those package managers only offer me K-3D v0.6 ,  which I regard as a waste of time.

But precisely on my Windows machine, I was able to get K-3D v0.8.0.1 as a binary, for which reason I wanted to bring my Windows box up to speed. I find it more of a pain in the neck, to do custom-compiles under Windows. For one thing, I still ony have Visual Studio 2005... Which was valuable once, and which is still the available target of ' cmake ' under Windows, but which is being supported less and less often by the Community.

Just so you guys don't waste any time on it, I wanted to emphasize that some of my earlier speculation in this thread was in error, thinking that Aqsis 1.8.x didn't accept Windows-style backwards slashes from the command-line. My testing showed that I could use the ' aqsl ' command from the home directory within my command console, to compile a shader in the K-3D directory, and to place the result in <HOME>/AppData/Roaming/.k3d/shadercache in one long line using the ' -o ' comman-line option, and that doing so succeeded.

It's just that one line in the .RIB File, which was not supposed to have any backslashes, just like the ' aqsisrc ' File isn't. And the good news was, that if the required information was supplied someplace else, Aqsis was well-behaved enough, to use the supplied search path.

Cheers,

Dirk

 

Bart Janssens
Offline
Last seen: 1 year 10 months ago
Joined: 12/22/2012 - 11:08
OK, thanks, this will be

OK, thanks, this will be useful when we update the bundled binaries to the 1.8 series.

Cheers,

Bart

Log in or register to post comments