STRONGLY EDITED: I have been experiencing different sorts of problems with the package pst-solides3d. They are related mostly -- but not exclusively -- to the fusing of objects. Moreover, I have not been able to compile correctly some of the examples which can be found in the main PSTricks site, one of which I had originally included here, although nobody gave any signs of having the same problem. Thus, I have decided to bring forward a couple of issues with my own code.

Firstly, in the next MWE I get a patch of the cylinder (a blue patch with the colors I have chosen) in front of the cube in a region where the former should be hidden:



\psset{lightsrc=50 20 75 rtp2xyz,%viewpoint,
viewpoint=50 15 60 rtp2xyz,Decran=50}
ngrid=4 16,
base=Cyl Hex]%(0,0,0)

The MWE is actually a mixture of one of those that can be found in the pst-solides3d documentation and another, a bit more complicated, of my own. Does anybody else get that wrong patch of the cylinder?

As a second example, in the next MWE I am trying to define a matrix of points in 3D space. The preamble is the same as for the MWE above:

\psset{lightsrc=60 20 10,
viewpoint=60 20 15 rtp2xyz,

Maybe this is not the most efficient way to proceed, but it is fairly simple. I have no problem when I have two of the index variables running and fix to a given value the third index (let us say it is \nz) by commenting the corresponding multido line and replacing \nz with some digit; but if I try to keep the three indices running, I have no output. I have tried also with the command foreach from the Tikz package, but the problem remains. Maybe there's something wrong about my code, but I'm not able to figure out what it is.

I have an updated distribution from a CTAN server which includes -- I believe -- the latest issue of pst-solides3d. My system is MikTeX 2.9 running on Windows XP. With other tries at pst-solides3d I've had the right outcomes, but the two above are among those in a bunch that have been giving me trouble. I think that those are enough for a start, though, and I may find out that it's just me doing something wrong in the code above.

closed as too broad by Paul Gessler, Andrew Swann, Mensch, user13907, yo' Sep 2 '14 at 11:48

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    I would suggest breaking these multiple questions into separate questions. You are more likely to attract answers if the questions are more manageable in size and address one question only. Furthermore, it's easier for future visitors to find and apply solutions to more targeted questions. – Paul Gessler Aug 19 '14 at 1:57

Browse other questions tagged or ask your own question.