By ASyme
#359084
Hi guys-
I touched on this in another thread, but I still haven't figured this out. What my problem is I can't see MOST of my textures at in the viewport in Cinema. It's just a horrid grey ghost town of nothingness. Pretty hard to texture this way. I was told to click this button (see first link) and all will be well. Great for a scene with a cube in it, but really shitty for real life projects with hundreds of objects.

Image

Now here's more what I get with a working scene file.

Image

This is actually better than what I get most of the time. At least I'm getting is this wood texture in two of the three places is mapped. Unfortunately, the place I need to see the mapping is on the floor which is just grey. Most of the time I'm just getting grey for all three.

I'm using an the latest ATI video card with drivers at 12.3 because anything after that is hosed in Cinema.

I don't get what's going on here. I just want to see my texture maps in the viewport. Right now, It's just cost me anther day because some maps are wrong and I couldn't tell while working on this. Super frustrating.

Are any of you getting this crap viewport display? Love to find a solution.

Thanks!
Alec
By JDHill
#359086
You are using Cinema R13, correct? I find its display to be a bit flaky with these viewport bitmaps. As to a workaround, although it might sound silly, try this: when you select (from the dropdown) the texture you wish to display, select it once, and then immediately select it again; at least, that is what works here. I don't think it's your drivers -- it behaves this way for me here too, and I'm using a Quadro. It looks like overly-aggressive caching in Cinema's OpenGL pipeline, since it will sometimes decide to show something entirely different than what it was given by the plugin. I've done some work on the viewport area for the next update (it should be available tomorrow), but it did not affect this problem; I'll look into it some more and see if I can poke Cinema a bit differently and get it to behave any better.
User avatar
By mashium123
#359093
probably not helpful, but your screenshot just shows a dark area where the floor would be.
just as if the viewport was set to be displayed in quick-shading mode. try changing to constant-shading and you'll see: all is full of light. :)
but that's probably not the problem. if the texture still is not visible, and the double-click trick mentioned won't help, i would do the - uncomfortable - workaround.
create a c4d-material using the path to the texture that's supposed to show up in your maxwell-floor material. attach it to your floor and do your mapping.
after mapping work is done, simply replace that c4d-material tag and use the c4d-maxwell-material instead. this way the c4d-maxwell-material will use the mapping-info that had been generated with your prior mapping-work.
By ASyme
#359199
JDHill wrote:You are using Cinema R13, correct? I find its display to be a bit flaky with these viewport bitmaps. As to a workaround, although it might sound silly, try this: when you select (from the dropdown) the texture you wish to display, select it once, and then immediately select it again; at least, that is what works here. I don't think it's your drivers -- it behaves this way for me here too, and I'm using a Quadro. It looks like overly-aggressive caching in Cinema's OpenGL pipeline, since it will sometimes decide to show something entirely different than what it was given by the plugin. I've done some work on the viewport area for the next update (it should be available tomorrow), but it did not affect this problem; I'll look into it some more and see if I can poke Cinema a bit differently and get it to behave any better.
Thanks Jeremy-
Yes, I'm using 13. Selecting the dropdown twice doesn't do anything for me. No matter what viewport setting I try (Gouraud, Quick, Constant) nothing works. Grey everything. That's tough for mapping. FIRE is great, but a simple viewport display would save me hours.

It would be epic if you could look into this. Do you guys need any Cinema beta testers? I'm been a beta site for Maxon for 13 years. I'd love to help find the bugs. I'm loving this render.

Thanks
Alec
By JDHill
#359202
I try to stay away from doing a lot of internal testing; generally, I try to keep things stable, and post pre-release builds right here on the forum for anyone who wants to give them a spin. There are two basic ways for a material to render itself in Cinema's viewport -- I'll try implementing the other one in the next build.
By ASyme
#359237
JDHill wrote:I try to stay away from doing a lot of internal testing; generally, I try to keep things stable, and post pre-release builds right here on the forum for anyone who wants to give them a spin. There are two basic ways for a material to render itself in Cinema's viewport -- I'll try implementing the other one in the next build.
Thanks Jeremy. I appreciate that.

Alec
Help with swimming pool water

Hi Andreas " I would say the above "fake[…]

render engines and Maxwell

Other rendering engines are evolving day by day, m[…]