|
-
Mar 11th, 2001, 11:08 PM
#1
Thread Starter
Good Ol' Platypus
VB gives this error:
_______________________________
|__________________________ _ 0X|
| Run-time error: 11 - division by zero |
| |
| [continue] [END] [DEBUG] [HELP] |
|______________________________|
(sorry, felt like being artistic)
When I set this:
With PT(PTT)
X=.X <---
Y=.Y
Z=.Z
End With
The funny thing is, it only gives this error when rendering the second particle (opengl), when it goes through the first particle everything works. I have tried EVERYTHING! All of the particles are the same as the result of debugging. Can you guys help?
All contents of the above post that aren't somebody elses are mine, not the property of some media corporation. 
(Just a heads-up)
-
Mar 11th, 2001, 11:40 PM
#2
transcendental analytic
nice art Sas!
again, i don't have any OGL experience so i can't say, are any of those variables properties, you either assign X on a property let, .X evaluate a property get, in that case do you have the source to this part or is it part of OGL or any other component you don't have access to?
Are any of them evaluated 0?
Use  
writing software in C++ is like driving rivets into steel beam with a toothpick.
writing haskell makes your life easier:
reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.
-
Mar 12th, 2001, 12:38 AM
#3
something is seriously wrong if you are getting a divide by 0 error without doing some division.
Z.
-
Mar 12th, 2001, 10:06 AM
#4
Thread Starter
Good Ol' Platypus
Yeah, neither of them are 0, and I dont think it does any division.....
What bothers me, is VB is probably "masking" the error. It's probably to do with something I gave an OGL call, and then it's in line #4 or something of that code, so it goes 4 codes down in MY prog, so it says that that is the error....
The strangest thing is, (like I said at the top), is that it works the first time around, but not the second...
All contents of the above post that aren't somebody elses are mine, not the property of some media corporation.
(Just a heads-up)
-
Mar 12th, 2001, 01:21 PM
#5
My suggestion is to "Debug by superstision (sp?)".
Comment some code out, run, see if it works, if not,
uncomment, comment something else, until you find
something that works. Check every scrap of info you
can find on whatever doesnt work, and study it for days
on end. It'll come to you eventually (I know =).
[edit]
More of VB's "whacked math" again =(
-
Mar 12th, 2001, 05:22 PM
#6
transcendental analytic
rightclick all values, and go for definition, and tell me where you get
Use
writing software in C++ is like driving rivets into steel beam with a toothpick.
writing haskell makes your life easier:
reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote