|
From: Greg R. <ne...@po...> - 2010-03-29 22:35:00
|
>> Oh, and one other gotcha with sdl-viewer: it appears that any X events >> (e.g., mouseover) while it's setting up the initial scene will lock up X >> input in a way reminiscent of the old Motif menu-focus-grab lockups. The >> mouse still moves, but focus doesn't change, and neither mouseclicks nor >> keyboard input are accepted. Since modern X no longer supports the old >> AllowDeactivateGrabs option, I can't verify that it's actually a grab >> issue, but that's what it feels like. (Logging in from another machine >> and killing the sdl-viewer process takes care of it.) > I'll give this a looksee once I've resolved the crasher bugs; but an > sdl-viewer specific bug might not get a very high priority from me. I was mistaken about the X events part--it occurs even without any mouse or keyboard activity at all (in fact, sole X event is initial expose, I think). It seems to be simply a one-in-20 (or so) error condition. I'm not certain, but I _think_ I saw it in freewrl yesterday, which may suggest a driver bug rather than either app. Newly seen rendering-model issue: with a half-transparent covering (a roof in this case), visibility of the underlying stuff depends entirely on the objects' order in the world file. This order... aerial-view ground texture (square) 50% tranparent roof house geometry house objects (more monitors :-) ) ...resulted in a completely invisible house and objects when seen from above; the texture is all that showed through the roof. This order, on the other hand... house geometry 50% tranparent roof house objects (monitors) aerial-view ground texture ...caused only the monitors and portions of the ground texture at the edges of the roof (i.e., without house geometry intervening) to disappear. Thus the only workable place for the roof is as the last geometry element in the file--unless one _wants_ the other stuff to go away, that is, which briefly proved useful when aligning the model with the aerial texture. Greg |