spike floor - GameCreators Forum

Author

Message

all of the above

16

Years of Service

User Offline

Joined: 2nd Sep 2007

Location: Anywhere an elf or kithkin may be hiding

Posted: 2nd Sep 2007 23:54

Link

It may not be very interesting but I made a spike 'floor' in 10 lines of code. I could have done it in less, but then it wouldn't be very readable.

+ Code Snippet

sync on:sync rate 0:i = 1:make object cone 1,1
for z=1 to 10:for x=1 to 10:inc i
clone object i,1
position object i,x * object size x (1),0,z * object size z (1)
next x:next z:position camera 0,5,5,-5
point camera 0,object position x (55),object position y (55), object position z (55): delete object 1
do
   sync
loop

I used the variable 'i' like an array. If you were to, say, move object 7 backwards a little, it would work.

Back to top

Profile PM

Libervurto

17

Years of Service

User Offline

Joined: 30th Jun 2006

Location: On Toast

Posted: 4th Sep 2007 02:50 Edited at: 4th Sep 2007 02:51

Link

I was bored so I decompressed your code

I've changed a couple of things so it works in DBC
That's a nice collection of cones you got there

+ Code Snippet

sync on : sync rate 0


make object cone 1,1
make mesh from object 1,1
delete object 1

i=1
for z=1 to 10
   for x=1 to 10
      make object i,1,0
      position object i,x*object size x(1),0,z*object size z(1)
      inc i
   next x
next z

position camera 5,5,-5
point camera object position x(55),object position y(55), object position z(55)

sync
wait key
END

[edit]
Oh yeah, never use DO LOOP like that, loops are for repeating things not for just waiting.

In programming, nothing exists

Back to top

Profile PM Email

Mr Kohlenstoff

17

Years of Service

User Offline

Joined: 7th Jun 2006

Location: Germany

Posted: 8th Sep 2007 15:56 Edited at: 8th Sep 2007 15:58

Link

1. You need one more sync (at least on my computer), otherwise the screen is just black.

Quote: "Oh yeah, never use DO LOOP like that, loops are for repeating things not for just waiting."

2. The do-loop-method has the advantage, that the screen is still refreshed, when the application was minimized, and in your version the screen is not updated again, so you don't see anything afterwards.

Back to top

Profile PM Email

Libervurto

17

Years of Service

User Offline

Joined: 30th Jun 2006

Location: On Toast

Posted: 8th Sep 2007 20:10 Edited at: 8th Sep 2007 20:15

Link

Quote: "2. The do-loop-method has the advantage, that the screen is still refreshed, when the application was minimized, and in your version the screen is not updated again, so you don't see anything afterwards. "

There's a check to see if the program has been minimized isn't there? Then you could sync after returning and that would save... whatever it saves

[edit]
found it: SCREEN INVALID()

So the new code would be:

+ Code Snippet

sync on : sync rate 0

make object cone 1,1
make mesh from object 1,1
delete object 1

i=1
for z=1 to 10
   for x=1 to 10
      make object i,1,0
      position object i,x*object size x(1),0,z*object size z(1)
      inc i
   next x
next z

position camera 5,5,-5
point camera object position x(55),object position y(55), object position z(55)

sync
while mouseclick()=0
 if screen invalid() then sync
endwhile
END

In programming, nothing exists

Back to top

Profile PM Email

Libervurto

17

Years of Service

User Offline

Joined: 30th Jun 2006

Location: On Toast

Posted: 8th Sep 2007 20:25 Edited at: 8th Sep 2007 20:26

Link

OK that's strange. I found that adding wait 50 before the sync made it work, but after that it doesn't work properly so forget about it.

Stick with the Do Loop thing if you really need it.

In programming, nothing exists

Back to top

Profile PM Email

Sorry your browser is not supported!

The 20 Line Challenge / spike floor