[daros]

I tried with the drop down and with the render icon.

[mappo]

same problem as oneshot
may someone help us?
thank u

[MetinSeven_com]

I thought it would be a good thing to open a sticky topic with known issues and bugs regarding the current RC1. I read that bitmaps don't work yet. One can not know such things unless these is something like a known issues thread.

Cheers,

Metin

[MetinSeven_com]

Thanks. I guess the "I've heard this" and "I've heard that" should be replaced by a solid little manual including known bugs and issues a.s.a.p., because we're currently all more or less trying to find our way in the dark, sometimes literally.

[3dtrialpractice]

Mike Verta,

JUST a BIG thanks to you for posting all yor helpfull notes, Wow that was quite a bit of reading to do this morning for me, and your posts really helped out a great deal!

THANKS SO MUCH FOR YOUR PATIENCE-AND ASSISTANCE

much apreciated
-Luke

[mverta]

Anytime, brother.

_Mike

[iandavis]

After following all suggestions posted on this forum I STILL have no ability to actually render. In fact I've had nothing but unexpected quits and various errors. When one installs software on two completely different machines running different OS, different chipsets, different graphics cards.. BOTH with an OS install younger then a month... both are almost virgin system... and BOTH showed that RC1 was basically unusable. From the people posting on the forum this seems to be a trend. When HUNDREDs of pretty snappy people are floundering around... getting no results.. oh ya... the software is FINE... it's just all of us who have a problem getting it to work. They have term for that... "bugware"

I think I can safely say that since I started using design software in 1988 this qualifies as THE MOST buggy software I have ever had the misfortune of installing.

I gladly offer NL... IAN'S BUGGIEST SOFTWARE, Lifetime Achievement Award.

All I need now is an adress for where to ship the award...

I have uninstalled and deleted RC1, from both of my machines, and from my perspective I'm still waiting for software that I consider even BETA level. There is no way on EARTH this is considered to be a release candidate by anyone except NL.

When I bought Maxwell they were calling it Alpha. I have seen nothing that shows me that it still isn't an alpha. A release candidate is supposed to have ALL of it's features functioning, with perhaps a few places to shift/add items... Bugs are to be expected, but the freakin installer doesn't even set up it's own application variables? This is completely unacceptable. NL couldn't face yet another delay, so they released a completely NOWHERE NEAR Release Candidate.

People are forgetting how things looked back when this was Alpha. They were promising a FINISHED version before the end of the summer! Now it looks like they are soooo far from a stable V1 that we may see it at the end of summer 2006. Frankly I wouldn't have plunked my money down had I known it was unusable and would remain so for more then another year. They have a word for that too... it's called FRAUD. Everyone seems eager to defend NL, but the FACT is that they either intentionally or through baby steps accidentally misled people to spend their money... that is literally a CRIME. So... After this peice of CRAP they are calling a release candidate I am now 100 percent disgusted. I'm telling everyone who askes to steer way clear of Maxwell. I had been going on about it back in the alpha days, and there were people who considered purchasing it... no longer though..

We are so close to the situation we don't realize how rediculous this is. When you explain the key points of the events leading up to the latest insult people often express shock, anger and disbelief at this situation... I get a lot of "YOU HAVE TO BE F**** KIDDING ME!?"

disappointed doesn't even cover it.

Ian.

[Ernesto]

I can create new cameras but they aren,t saved with the file. If I close the scene, and open it again all the cameras would be lost.
The render Buttom makes the software crash.
The menues do not work in case the mouse is not in the current viewport.
The preview buttom makes Maxwell to crash.
The Ctrl P command makes Maxwell Crash
I have been trying to import from many formats, and everything failed except a very old DXF Acad 12 format.
How can I change normals?

I am totally dissapointed!
this software is not ready at all, I doubt you will finish it by this year.
To be realistic it seems you need 1 more Year.

ERnesto

[max3d]

I installed and got it to preview AND render in about five minutes. Sofar I did'n try anything beyond Mike's test MXI scene, but it works well, doesn't crash. I can adjust materials and camera's without problems.

What doesn't work for me is Resume Render. Whatever I try it fails. The next thing which won't work for me is the attenuation in the material editor. I can't get it below 1. Any advise?

Ah, found Tom's post regarding attenuation:
"1-Set transmittance color just like you do for transparency color before.
2-Set attenuation distance as at least as big as your object. This value also controls absorbance and when you set it too high, you will encounter loss in saturation of transmittance color. 10 mm for 1 cm thick object will absorb 50% of total energy transmitted.'

So forget about the second complaint, I just didn't understood these sliders.

[max3d]

And in the real renderer the preview doesn't show anything. It keeps black. Doing something wrong?

[daimon]

I just want the beta way for rendering from maya (for me) to work with RC1 version of renderer, I tried to do some "tricks" with the beta files to make it to work but it seems that the rc version doesn't like the exports that maya plugin does and freezes.
And btw did they tried it before they send it out to users? or did they send an old build by mistake?

[Becco_UK]

Before I forget. Thank you to Mverta and Mihai Iliuta (in another thread) for getting me to the point where hitting render fires Maxwell up and produces an image.

Not happy with the quality and other things, especially lack of Cinema plugin, but I do appreciate the help I recieved from those two.

Still very disapointed with the overall Maxwell situation though. To Next Limit Team: No more Sangria until fixes have resolved the many problems.

[DavidR]

This is supposed to be a RC... why should there be so much to 'get through'?[/quote]

Oddly enough, I'd say because all the people who screamed NOW NOW got what they wanted. They got it NOW.

Alpha = new features, beta is feature-locked. This RC thing is completely out of left field, as far from beta as possible. Why didn't you give us PAYING users access to each new build along the way? We would have helped you avoid this fiasco. What an immense letdown. The installer's crap, Max renders grainy b&w, and Maxwell Studio doesn't render anything. WTF? I'm thinking that if someone's pissed enough, you may get hit with a class action lawsuit.

This is not a beta; I'll tell you what a beta is: we use Vray standalone 32 and 64-bit beta with no issues. That's a beta, and if something were to screw up, I'd be OK with it because it's a beta, and because Vlado didn't make me pay $500 for it because it's a beta. Frankly, I don't know why he doesn't release it, but he knows best why it's a beta. Did I mention that it's a beta? NL should have built the standalone separately while maintaining the Max plugin (screw Rhino and C4D, etc:).

[DavidR]

You're asking me to be practical, and suggesting that the practical thing to do is to try and figure this shit out. What are you thinking?

What - specifically - do you think the practical thing to do is, right now, to make Maxwell a more stable application?

_Mike

You keep talking about stability, as if the odd random crash is the issue, well here's the issue: it doesn't f***ing work, period.

[3dtrialpractice]

"Maxwell Studio doesn't render anything"

its weird, Maxwell Studio renders Fine for me, No crashes, Well acctually I had ONE crash of the RENDERER, not the studio, BUT it was MY fault, I had assigned the same Object 3 Shaders,, and when I hit the render button It looked like it was gonna render but at smp1 it crashed, I QUICKLY fxed this by lookign at my scene and realized that I had put 3 shaders on 1 object by mistake... Once I deleted the 2 extra shaders, the scene rendered fine.... so that crash was totally my USER ERROR..

So in my situation the Maxwell Studio Works well!- renders fine
In other ppl situations they cant render at all.

I'm not sure its as much Maxwell Studios fault as it could be HArdware Issues with some machines, maybe some weird file issuses.. One never knows, with PC's its hard to make an app that works 100% on all pc's becasue the nature of pc's, everyones got different Hardware and different video cards, differnet setups, differnert OS's , etc..., From what some ppl said when they move the camera it crashes(sounds like video card issue not MXstudio), Mine hasnt crashed yet (knock on wood).. ive tried to move the camera around hit differnet keys fast, Its slowed down to think when ive bumped up my shasder preview settings but that was it, then worked fine again...

So these problems ppl have may be much related to their own personal computer setup...

Dont be too hard on em now.. lets just be patient, apparently according to the reps here (the beatatesters) they already are making fixes to this RC..

Its some drama, but to me its exiting, Its new, and 'm sure in a few weeks, ppl will have totally forgoten how rough the First day of the RC release was becasue alot of problems will be wrinkled out, and ppl will be rendering like crazy.

-sorry that your studio isnt working, but hang in there.