1. Exotica & crash
Tämä on moniosainen MIME-muotoinen viesti.
------=_NextPart_000_0007_01BF05F1.1EE2CAE0
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I had some weird problems with my server, so i haven't been able to =
write to the list.
I've been reading messages from list server's pages, and some of 'em =
have helped me a lot, thanks :)
still got one problem unsolved: my machine still crashes while using =
exotica and files I have edited/created by myself. Could you, Todd, see =
what's bugging my source? I have included it with this mail.
"soon registered user too"
--Talvitie
------=_NextPart_000_0007_01BF05F1.1EE2CAE0
name="t3de.ew"
Content-Transfer-Encoding: quoted-printable
2. Re: Exotica & crash
Hiya,
Talvitie wrote:
> still got one problem unsolved: my machine still crashes while using exotica
> and files I have edited/created by myself. Could you, Todd, see what's bugging my
> source? I have included it with this mail.
function MainLoop()
if ProgState=0 then
LoadWorld()
ProgState=1
elsif ProgState=1 then
for c=1 to LastCam do DoThe3D(c) end for
^^^^^^^^^^
I commented out the for loop that uses your DoThe3D(c) routine
and then it didn't crash my machine anymore. Since I don't know
the 3D math stuff quite yet, I haven't a clue why this
function crashes...
Hope this helps ya somehow...
- Todd Riggins
3. Re: Exotica & crash
Doh, I think I do have a clue... mabie your drawing pixels outside
the surface(screen). Currently, Exotica doesn't like that sort of
thing. I'll slap Exotica around and make it like it in the next version.
- Todd Riggins
4. Re: Exotica & crash
Todd wrote:
>Doh, I think I do have a clue... mabie your drawing pixels outside
>the surface(screen).=20
No I'm not. Well I might been in the file I send you, but I fixed it and =
it still crashes.
Am I writing into vars(in DoThe3D) that are used by exotica?
>Currently, Exotica doesn't like that sort of
>thing. I'll slap Exotica around and make it like it in the next =
version.
This will make the routine slower so I have a suggestion:
include global integer into your .ew file which will choose from safe =
and unsafe modes.=20
Safe (default?) =3D you can't crash=20
Unsafe =3D Fast routines. =20
User could then use Safe to test and Unsafe after this when having need =
for speed
Thanks for trying to help :)
--Talvitie
5. Re: Exotica & crash
On Fri, 24 Sep 1999 23:15:49 +0300, Talvitie <smtoa at SAUNALAHTI.FI> wrote:
>>I'll wait for it, I guess. If anyone else has an engine
>>that does what I need, don't hesitate to let me know.
>>I'll ultimately use the one that does the best job
>>in the least time.
>>
>>later,
>>Lewis Townsend
>
>
>cause you don't really need the engine source and all you want is bitmap(?)
>files, why not use some executable ray tracer to do the job. You can
>propably download one from the web. I found POV-ray (rendering engine for
>Windows 3.x) some time ago. Here's what it's documentation tells about it:
<Snip>
I use Pov-ray for win32 to do quite a lot of the graphics in my games. It's
a lot easier than drawing all those sprites by hand, specialy if you need
rotation and a lot of animation.
>I haven't needed it almost att all, but it should be pretty much easy to
>use. I haven't figured out how to save images, but one way could be using
>f.ex. Paint Shop Pro's image capturing if there isn't easier way.
Images are automaticly saved to a bitmap file, if your input file is
"3d.pov" your bitmap will be "3d.bmp".
-Mark.
6. Re: Exotica & crash
Talvitie wrote:
>
> Todd wrote:
> >Doh, I think I do have a clue... mabie your drawing pixels outside
> >the surface(screen).
> No I'm not. Well I might been in the file I send you, but I fixed it and it
> still crashes.
> Am I writing into vars(in DoThe3D) that are used by exotica?
Unless you are using a global variable that is defined either in
ewin32lib.ew or exoitca_api.ew inside DoThe3D(), I wouldn't imagine
that would be the case. I skimmed through DoThe3D() code and didn't
see any Exotica routines, right?
> >Currently, Exotica doesn't like that sort of
> >thing. I'll slap Exotica around and make it like it in the next version.
>
> This will make the routine slower so I have a suggestion:
> include global integer into your .ew file which will choose from safe and
> unsafe modes.
> Safe (default?) = you can't crash
> Unsafe = Fast routines.
> User could then use Safe to test and Unsafe after this when having need for
> speed
That is a good idea. But the slow down will only occur if the you draw
outside the screen area, just like what I have now with the RECT_BLIT
routines that I'm currently working on.
But since I'm wanting to make some CLIPPING routines some time down
the road, I can go ahead a make a single Exotica routine
that the user can set if they want clipping activated or not
which would effect all Exotica functions that uses clipping.
> Thanks for trying to help :)
No problem. If you have any other question about this , please ask.
I will try to look at your proggy again sometime this weekend to
try to see what's up.
> --Talvitie
