#Small R3 bugs.
10 messages in this thread
Gary et al-
R3 is _GREAT_! I am still going through the very well written new tutorial
and discovering new wonders.
I have, though, discovered a couple of small non-life-threatening bugs that
I thought I'd pass along.
1) The delete line (@L), delete end-of-line (@E), and delete word (@W)
commands in the editor are broken. Also, only one of my two Delete keys
works.
2) This is a strange one. In the 3D Editor render a viewport at 640 x
480. Now go to the Materials Editor and render a few sample spheres
of any material. Everything's normal so far. Now go back to the 3D
Editor and re-render the viewport only this time change to the VGA
320×200 driver. Go back to the Materials Editor and re-render the
sample spheres. They are no longer spherical but ovoid, and cubes are
flattened too! I haven't found a way to restore their proper aspect
ratio short of exiting 3DS and re-starting. Changing the rendering
resolution back won't do it.
Gary's on a little well-deserved vacation for the next 4-5 days. (his
big block of time off is coming in November) I'm glad you like the
new release. Regarding your comments:
1) Very astute about the @L, @E, and @W commands in the Text Editor
not working. That help screen in the text editor was actually written
by someone in the doc group and it slipped by without the programmers
ever being told that it was supposed to work that way. Oh well.
2) That IS a strange one. In fact, you get the prize for finding the
first (albeit incredibly obscure) bug in R3. Congrats! We'll put it
on our list for when we do the next update. I don't think that
that's going to be a big problem… worst case is just save your
work, exit the program and come back in
I too have been enjoying R3 enormously, but have also had a little
trouble. In the first few hours of using R3 it has crashed 4 times;
it happens after completing a render, then it either hangs before or
after returning to the editor screen. The only escape is with a cold
boot.
If you're having problems with the system crashing after rendering,
it's DEFINITELY due to a hardware problem on your end. If you'd like
to confirm that with Gary when he gets back, send him an email and
he'll get back to you next week.
Willdo. Actually, it seems to be a problem involved in display
screen switching; today I tried viewing some of the new maps on the
World CD and the computer hung up again. Could it be something on
Vibrant's end?
I've found that problems with display modes and computer lock-ups are
invariably due to memory conflicts. But that's my experience. What
kind of memory management are you using? Are you excluding
everything used by video? I ask, because I had things working
seemingly fine, then Bang!, one day I started getting lockups.
Exclusions in my QEMM (and EMM on another machine) did the trick.
Interesting; I'll dig out my Qemm and Hercules docs and see if I can't bash out
some sort of solution.
Thanks. Ian.
I too am experiencing sporadic crashes when rendering. I too
suspected Vibrant, and then QEMM 7.0, but I've excluded everything in
my system (almost). Still happens. If I stumble across a solution,
will post here.
Some people have had problems with their shadow ram being turned
on… you might check that. Good luck… and of course, if you can
provide more specifics, some of the hardware experts here on the
forum might be able to give you some help.
>> …the first (albeit incredibly obscure) bug in R3.
Jack-
Well, I DID say they were _small_ bugs.<G>
Anyway, congrats right back to you guys for a great new release.
Greg