Yeah, I JUST (yesterday) got through dealing with John Brock, whose FIRST reply to my PLEAS for HELP - THIS time around (6th or 8th try …) I was told SERIOUSLY : "… to hit OK when closing out the dialog box to save changes … " SERIOUSLY ?!? (I have the email.)
Ok, we went back and forth for a few days, me AAGGAAIINN detailing for the ump-teenth time my system configuration, sending sample models and the WHOLE FRKN NIGHTMARE, only to FINALLY gat an admission that they "… have disabled OpenGL supported Antialiasing support in RH-5 and have no plans to re-engage it, as they no longer support RH-5 " (wait - I’m GOING somewhere with this RH-5 thing … ) and that they consider THEM having DISABLED this CRUCIAL FEATURE as a Bug. A FRKN BUG ! (I have the email). Apparently this extends to RH-6 TOO ?!?
Upon subsequent conversation on the subject, I made it CLEAR that this was a GENUINE issue, and he let slip that he "really felt the solutions they implemented in -6 should be the preferred approach, me NOTING here that HE previously had specifically DENIED any subsequent “UPDATES” to RH-5 once RH-6 was released, EVEN AFTER I pointed out THAT couldn’t be right because I SPECIFICALLY responded YES to the question did I want to update (I WAS IN 5 AT THE TIME) since an "Update is(was) available …? " starting the whole problem process we’re now trapped in dealing with.
NOW we learn that at SOME point, presumably NOT in an update he SAYS never occurred, THIS FUNCTION WAS DISABLED. Now, based on YOUR findings this SEEMS to extend to RH-6 as well ?
ONLY POSSIBLE conclusion - THEY are INTENT on moving us to “Raytraced”, whether we can afford it or NOT (TIME more than $$, as I’ve ALREADY sprung for the $300 for Raytraced, with only MARGINAL results - I CAN give details - I’ve kept ALL my notes … ), even tho Rendered Viewport USED to be PERFECTLY SERVICEABLE (and OFTEN GORGEOUS - which MAY actually have been the problem … ), and in MANY ways FAR SUPERIOR to ANYTHING put forth in any attempt to replace it ( I EVEN tried “Flamingo” - $$$ and was APPALLED at the time it took for ONE marginal render … ) .
So, using some OTHER tricks I’ve tried in the past, and NOW having problems with THEM too, I was even re-considering trying to migrate forward to -6 AGAIN for now the 8th time (I’ve got the license, but "Raytraced keeps interfering with EVERYTHING visual … ), I see based on YOUR response here that even THAT seems a no-go ?
SO SORRY for your trouble, bud and SINCERELY - THANKS for trying !
SERIOUSLY don’t know what my NEXT steps will be, except to tell my CLIENT that instead of getting the first check-run (beautiful, and OFTEN equal to or surpassing their expectations OR NEEDS … ) of my animation by “…noon TOMORROW …” (if we are talking 8:am Monday morning, NOON Tuesday !!!), they will have to wait for a MARGINAL result until well toward the END OF THE WEEK, and LIKELY well into NEXT week . Seriously- I keep ALL notes …
If you or ANYONE comes up with ANYTHING - PLEASE SHARE ? Suddenly I’m NOW having problems with the BONGO-2 Video Compiler, standard Windows output NO LONGER playing on standard Windows Media Player - the medium I circulate ALL of my output to clients in, because for the last 18 years ANY client could play an animation on ANY system, ESPECIALLY a windows one, with NO ADDITIONAL SYSTEM REQUIREMENTS. I’ve put up a CODEC-where-to question here on another thread . It MAY be a max-resolution issue, we’ll have to see.
Maybe SOMEONE will be able to offer some usable insight ?
Thanks again for trying,
ALL the VERY BEST to you and yours, from Texas - C.