Poser 8 Forum

I gave a try to see if poser pro 8 would work in CrossOver (tried with Pro on Linux) it does.
providing you use the closed-source ATI drivers, I need to test with nVidia drivers (desktop has a Geforce 9800GT, laptop a Radeon mobility HD4550...),
but the open-source (radeon) drivers don't work (Poser will install, but won't run)

one problem though, in poser there are tool windows, these contain the active view-port, library, etc. etc.
these windows can be moved inside posers main window, at least, they can be on windows.
but not under crossover, when trying to move them, or when accidentally clicking the title bars (or a other place where the window can be moved) will cause (in my case) KDM to crash.

basically it's not such a problem, just don't move them, but since it also crashes if you accidentally click any place dragging on which would move the window.
it makes a big problem, it's likely you will indeed click somewhere like that by accident, anything not saved then will be lost.

I just lost all work on a pose, I can redo it, but it does take a while to make the settings right, and I wanted to save it when I managed to crash KDM...

does anyone know something I could try to make it sure it will either move the windows, or ignore any clicks meant to move them?
clicking on buttons, or text fields etc. works fine since the click doesn't focus on the window itself.
I need a way to make sure that any click that should focus the window is ignored, so that it won't crash, other then that, everything work, including rendering.
(at least anything I tried so far, which is: loading models (that I copied to "C:\" program files\smithmicro\poser\content\, haven't tried loading them from a zip file) , modifying parameters, pan and rotate the camera, and rendering)

update: just tried on my desktop with seems to be the same, works with closed source, not sure if it works or not without, since I already had those drivers on my PC.

Hi,

Umm...'KDM'?...you mean the session manager is crashing? (as opposed
to the WM?)...let me know. Otherwise I would try this in a different WM
to see if it's that or something else. I would also ensure that no desktop
effects are active (compiz and other lollypop shizzle like this) to see
if they're responsible. I would also try using the 'emulated virtual desktop'
feature in winecfg to see if running it like that made any difference..

..also, if you could run things with debugging options enabled and recreate
the event, something in those logs may clue a clue as to what's going on...

This'd be my 'off top of the head' ideas to try 8)

Cheers!

eh, well, it may not be KDM, but it's not KWin either, everything graphical dies.
it KWin would crash I'd lose the window-borders but I would still be able to use X, which I can't then.

the desktop effects are not responsible, it also happens if I turn them off.

edit: tried the emulated desktop, it does cause them to work, so I can move them and poser won't crash, but window drawing does go somewhat wrong, when I open the library drawer the windows lose there visual content, though when I close it again they are redrawn correctly. (the windows within poser I mean then, not the poser main windows).
menu's also stay in view until I click outside the menus.

poser doesn't have any debug options as far as I can see, and I can't find any in crossover either...
I'll take a look at the logs anyway though, there may be something usable.

Hi,

Ok...I only posed the question because there's a significant difference  

between KDM crashing as opposed to the WM crashing (or X itself)...is this a
user directory installation of crossover or system wide in /opt ?....

Regarding debug, I was referring to obtaining debuglog of the event via
crossover, not by Poser itself...see;

http://www.codeweavers.com/support/wiki/SubmitTechSupportLog

There may perhaps be a clue in that log that gives a telltale of what was
going on at the time which causes the behavior. If it's crashing X or such,
that debug will likely be in /var/log/ directory which would telltale what
happened there (at system level as opposed to wine level). If the logs or
their content confounds you, gzip them & upload to a free repo like rapidshare
or the like and post the download URL back here - that way others can grab
them and have a look...

Cheers!

system-wide, in /opt.

as for the debuglogs, if I look at /var/log after enabling debugging, I don't see a for it.
there is a debug log, but it's latest entry is from a hour ago, I just ran poser so that entry it not relative to the error.
it would seem that whatever happens causes crossover to be unable to write to log. (possibly crossover also crashes and thus has no time to perform any I/O operations)

....<grin>,,,,perhaps I should been a little bit more crystal here ...

...logs in /var/log will be system logs....ie; if KDM is crashing,
that would be in /var/log/kdm.log or if X is crashing that would be
in /var/log/Xorg.0.log etc etc....

With crossover debug, the log will be somewhere else....you can do this
via the crossover GUI....start cxsetup (manage bottle), highlight the
bottle in question, click 'Run Command..', use the 'Browse' button to
navigate to the Poser exe file, click Open. Click on the Debug Options
widget, click Create Log File, pick the debug channels you want to look
at (I's try +seh +tid +x11drv for starters)......hmmm.....

...that's obscure, it doesn't actually tell you where the debuglog is
going to end up ( ie; /full/path/to/logfile)....I must mention that to
one of our Illustrious Ninjas....a commandline example of this GUI method
would be...;

/opt/cxoffice/bin/wine --bottle [bottlename] --debugmsg=+seh,+tid,+x11drv --cx-log ~/poser_debug.log --cx-app NameOfProgram.exe

Using the above command, the debug log will be in your homedir and be called poser_debug.log

...keep me posted....

Cheers!

I know /var/log are the system logs, but still, it's strange nothing is there, since it does affect the system.

anyway, log from crossover:
most of the log seems useless (createbitmap (color) sizexsize position, etc. etc.)
....but the last bit:

001e:trace:x11drv:X11DRV_ExtEscape SET_DRAWABLE hdc 0x23c drawable 9e gl_drawable 9e pf 0 dc_rect (0,0)-(1600,900) drawable_rect (0,0)-(1600,900)
XIO:  fatal IO error 11 (Hulpbron is tijdelijk onbeschikbaar) on X server ":0.0"
      after 628 requests (557 known processed) with 0 events remaining.

just to be sure the complete log (archived as poser.log.tar.gz)

also: it doens't say where the log will be placed, because it asks if you select to make one ;)

Mmmh...discovered that about logfile placement about 5minutes ago ;)

[perhaps I think that's too hard and it should just say "I am going to
put this in your homedir" 8)

...but...I picked the right debug channel by the looks....that'll be
the culprit. There is some garb over at WineHQ on this title, but none
of it seems related to what you're seeing;

http://appdb.winehq.org/objectManager.php?sClass=version&iId=17442

...interesting log though -- that call actually appears to complete in
the log earlier on...looks diabolical and beyond the scope of my knowledge
here -- immediate suggestion would be to email info@codeweavers.com with
a brief on the issue, attach the logfile and see if any of the codeweavers
Ninjas/staff have a thought on that one....

How did emulated desktop mode go?...same problem?

Cheers!

using the emulated desktop they do work, but drawing is rather slow, which is rather useless for in a 3D program.... 😋

...hmmm....okay...if you haven't already tried installing the directx runtime
package into the same bottle, I would try that to see if it helps speed to screen...

..You might try including the following registry key;

REGEDIT4

[HKEY_CURRENT_USER\Software\Wine\Direct3D]
"DirectDrawRenderer"="gdi"
"OffscreenRenderingMode"="fbo"
"RenderTargetLockMode"="auto"
"UseGLSL"="enable"
"VideoMemorySize"="512"

I would try changing "DirectDrawRenderer"="gdi" to "DirectDrawRenderer"="opengl"
The key "VideoMemorySize"="512" should be set to the amount of videocard ram you have.
Other keys here may also have an effect on performance...have a read over at wineHQ
for possible values;

http://wiki.winehq.org/UsefulRegistryKeys

I would still recommend that you email info@codeweavers.com on this one...

Let me know how you get on....

Cheers!