Path: chuka.playstation.co.uk!news From: "Alex Herbert" Newsgroups: scee.yaroze.freetalk.english Subject: Re: Destruction Of Arrays.... Date: Fri, 31 Mar 2000 13:42:47 +0100 Organization: PlayStation Net Yaroze (SCEE) Lines: 45 Message-ID: <8c26d3$pfl1@chuka.playstation.co.uk> References: <38DBC707.49543F25@chilternmag.demon.co.uk> <8bh0kg$7291@chuka.playstation.co.uk> <38DE47BA.331E1477@chilternmag.demon.co.uk> NNTP-Posting-Host: 15.02-03.quay.dial.plus.net.uk X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Hi Chris, how's it going? Now let me guess... you're trying to implement multiple levels in Drum'n'Race, right? For everyone else's benefit I ought to give a quick explanation. I knocked up a quick example of a 'Micro Machines' type game for Chris a little while back which he is using as the basis for his game. The thing is, I hard coded the map data with static data (crude, I know) and I'm assuming this is now becoming a problem. So Chris, the best way to do it would be to write a level editor and fill the array from data files. (A simple BG editor will not do as the BG is only part of the map data.) However, I have a solution which I think will suit you better at this stage. Rather than working on the static level data directly it would be better to use intermediate map arrays. These arrays should be big enough to hold the largest level, and you'd simply copy in the relevant map data (with 'for' loops) just before the start of the level. Then, when moving onto the next level, the old data in these arrays can be safely overwritten with the next level's data. Anyhow, if you need any more help, or if I've completely missed the point, mail me. Alex Chris Wallace wrote in message news:38DE47BA.331E1477@chilternmag.demon.co.uk... > The problem with that.. (tell me if I read it wrong).. is that the actual array > is very eratic, it's not just lots of 0's and then lots of 1's. > so counting out which int to start the loop at and which to finish it at for > every change will be incredably timeconsuming... here is an example of one of > the arrays: > > Chris. > >