BRAIN FART GUYS! HELP
Blitz3D Forums/Blitz3D Programming/BRAIN FART GUYS! HELP
| ||
ok, im not getting anything in the screen... quick question; do i HAVE to create the camera first BEFORE loading Meshes?? or does it not matter as long as the Graphics3D is created first? |
| ||
It doesn't matter. There must be something else to blame. |
| ||
nah , im saying that meshes are MAV'ing. i just dont remember i want to rule this one out |
| ||
use debug to see if the meshes are loading, they'll be 0 if they're not. |
| ||
Always helps to show your code too :o) Are you modifing the meshes at any point? |
| ||
just add a stop statement after the mesh loading area, and check your variables! |
| ||
I don't get it. You first simply say nothing is showing on-screen, and then you say you're getting a MAV. |
| ||
Twas like that other guy who's code magically vanished ;o) Strange goings on eh? |
| ||
Twas like that other guy who's code magically vanished ;o) Strange goings on eh? its a conspericy lol jk. post some code though.are you using renderworld and flip |
| ||
Eh? "Neochrome" is hardly a new user. I expect a full explanation or I shall be writing quite a stern letter to his parents. |
| ||
Lol. i've been coding a while sure, but just having some troubles with meshes loading one minute, the next not! still unsure what the problem is i've tested this graphics3d 320,240,16,2 me% = loadmesh("ufo.b3d") its wierd, as it works one minute, then the next, 0! actually.. thinking about it! THIS computer is doing the "im developing memory fatigue!!" just wondered if it was vital to create a camera!? just that i load meshes BEFORE the camera to avoid rendering accidently (my graphics card is not good so im working around it -- FOR NOW) Thanks anyways |
| ||
'me%'? Why isn't it just 'me'? I never use the '%'. Why do you use it? |
| ||
You only need the camera to render. It's absense shouldn't cause a mav. its wierd, as it works one minute, then the next, 0! If that's the case, then the variable you're using to hold the mesh handle is probably getting set to zero at some point, or you may have it declared as a local variable when it needs to be global. |
| ||
Please use a descriptive topic title next time. |
| ||
Cool ANSWER i needed Bill thanks :) however, i ALWAYS use me% to ensure that the pointer number IS an integer! |
| ||
however, i ALWAYS use me% to ensure that the pointer number IS an integer! Declare all variables is always a good practice. |
| ||
Const .... Globals .... function local end function IN THAT order ;) |
| ||
Mmm, I never do this with a mesh. Why would it change to a float? |
| ||
i've found it happens! i've lots mesh's for some reason, there was a bug in the past that didn't create ints correctly. since using them NEVER had a problem, only my bad programming! :D |