Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

DarkBASIC Professional Discussion / This bug has me seriously confused. Multicameras are nice, but only when I ask for them!

Author
Message
Ian T
23
Years of Service
User Offline
Joined: 12th Sep 2002
Location: Around
Posted: 26th May 2003 23:11
If I run this code every loop:

set cursor 750,584
print "FPS: ",screen fps()
set cursor 0,0

Then I get a second camera starting at 0,0 and ending around 640,300 (guesswork). It takes up more than half of the top of the screen in 640x480 mode. If I comment out the Set Cursor command... it dosen't happen. By the way, the camera seems to be at roughly the same position, but it is obvious that the view is different.

I don't use Make Camera commands anywhere in my code. In fact, the only camera commands I use are at setup, as follows:

set camera range 1,600

I'm pretty sure this started with Patch 4.1.

I can post the full source if absolutely neccessary, but a simple moving-around boxes demo should show you what I mean.

As an aside, the text is NOT getting printed like it should.
--Mouse

Famous Fighting Furball
Kentaree
23
Years of Service
User Offline
Joined: 5th Oct 2002
Location: Clonmel, Ireland
Posted: 26th May 2003 23:55
Hmm, strange. Post the code, because it would be interesting to see how this happened. A solution might be to use the text command:

text 750,584,"Screen FPS: "+str$(screen fps())

Whatever I did I didn't do it!
Shadow Robert
23
Years of Service
User Offline
Joined: 22nd Sep 2002
Location: Hertfordshire, England
Posted: 27th May 2003 00:51
set camera range works fine for me... i'd contact Lee or Mike talk to them about the problem

Within the Epic battle of the fates the Shadow and the Angel will meet. With it will harbinger the very fight of good vs evil!
Ian T
23
Years of Service
User Offline
Joined: 12th Sep 2002
Location: Around
Posted: 27th May 2003 01:11
It's not the set camera range that's the issue. I can negate that command and still have the problem.

Kent-- yup, but it still annoys me. Just in case you were wondering, the all-use

scrnfps$=Screen FPS()
Set Cursor Screen Height()-Text Height(scrnfps$),Screen Width()-Text Width(scrnfps$)
Print scrnfps$

does the same thing.

--Mouse

Famous Fighting Furball
The Big Babou
23
Years of Service
User Offline
Joined: 10th Feb 2003
Location: Cyberspace
Posted: 27th May 2003 01:17 Edited at: 27th May 2003 01:23
easy one:

if you run your program in 640x480 and set your cursor to 750,584 what could be wrong?

try setting the cursor to 10,10
The Big Babou
23
Years of Service
User Offline
Joined: 10th Feb 2003
Location: Cyberspace
Posted: 27th May 2003 01:24
or change the resolution to 800x600
ToXic
23
Years of Service
User Offline
Joined: 8th Sep 2002
Location: Australia
Posted: 27th May 2003 01:25
If I set my display to 800*600, and use set cursor 750,584 this
places the text part of screen to the bottom right, I get what looks like a second camera view, now if I change it to set cursor 750,500 so it is on the screen this fixes the problem, for me anyway.

Weird one, looks like part of the screen has been moved up as it would if you you were to print of screen in 2D.

report it, I think it is a bug for sure.

ToXic.
The Big Babou
23
Years of Service
User Offline
Joined: 10th Feb 2003
Location: Cyberspace
Posted: 27th May 2003 01:47
why is it a bug? i think there is a misunderstanding. :-s

you can't set the cursor off the screen.
set cursor 0,0 prints your text in the top left corner, set cursor to 639,479 (at a resolution of 640x480) the text is printed in the bottom right corner of the screen. but setting the cursor to 639,479 is too close to the border of the screen, in fact your text wouldn't be visible.
but setting your cursor off the screen, for example set cursor 641,481 (at 640x480) will cause this strange behavior of the screen. i hope you get the point
Shadow Robert
23
Years of Service
User Offline
Joined: 22nd Sep 2002
Location: Hertfordshire, England
Posted: 27th May 2003 02:19
i think i'm actually missing the current problem, and i wouldn't mind seeing the source - or some source which would have the problem, i figured when you said the problem involved the camera and then noted the camera range that was the problem.

though i think TBB is right, if your trying to type text so close to the edge its bound to not appear or seem like the screen is mostly taken up - but then thats just command sense or atleast logical sense

Within the Epic battle of the fates the Shadow and the Angel will meet. With it will harbinger the very fight of good vs evil!
ToXic
23
Years of Service
User Offline
Joined: 8th Sep 2002
Location: Australia
Posted: 27th May 2003 03:00
Ok run this, it shows the problem for me.

ToXic.
The Big Babou
23
Years of Service
User Offline
Joined: 10th Feb 2003
Location: Cyberspace
Posted: 27th May 2003 03:38
ok, i tried it. (it's beautiful ). i knew before, you mean those "cracks". i don't know how to describe. the description with the 2nd camera is best so far.

setting the cursor to 750,576 works; set cursor 800,576 works; set cursor 750,578 doesn't work. then you can see those "cracks". what brings us to the conclusion: the x value (set camera x,y) may be greater than the screen width; the y value has to be around 5% smaller than the screen heighth. i recently discovered it is also linked with the text size.

ok, maybe it's a bug. but it's a minor bug. i would like to see the free flight commands fixed before such smaller things. 750,576 is at the bottom right corner for me. but now I#m tired and go to bed. i'll look more into it tomorrow.
Ian T
23
Years of Service
User Offline
Joined: 12th Sep 2002
Location: Around
Posted: 27th May 2003 04:42
Oh, come on. I *said* that I had run it in 800x600. Why don't people actually read the post before dismissing it, especially when they already know that the bug is there? Jeez...

It is NOT a minor bug. I should very well be able to set the cursor within the screen resolution without having screen artifacts rupture my visual display.

--Mouse

Famous Fighting Furball
Shadow Robert
23
Years of Service
User Offline
Joined: 22nd Sep 2002
Location: Hertfordshire, England
Posted: 27th May 2003 04:42
theres a bug in the "Print" command... it can't be used with the "Screen FPS()" function, there might be some others.

Email Lee your source and note that it works fine with the "text" command

Within the Epic battle of the fates the Shadow and the Angel will meet. With it will harbinger the very fight of good vs evil!
Ian T
23
Years of Service
User Offline
Joined: 12th Sep 2002
Location: Around
Posted: 27th May 2003 04:49
Yes, text is a fine tideover.

*Mails bug*

--Mouse

Famous Fighting Furball
The Big Babou
23
Years of Service
User Offline
Joined: 10th Feb 2003
Location: Cyberspace
Posted: 27th May 2003 12:51
Quote: "Oh, come on. I *said* that I had run it in 800x600."

in mouses 3rd post.

Quote: "It takes up more than half of the top of the screen in 640x480 mode. "
in mouses 1st post.

Oh, come on. i *read* your post before answering it.
Ian T
23
Years of Service
User Offline
Joined: 12th Sep 2002
Location: Around
Posted: 27th May 2003 19:33
I said its X dimension was around 640. I couldn't have known this without testing another screen mode.

--Mouse

Famous Fighting Furball

Login to post a reply

Server time is: 2026-07-11 06:07:15
Your offset time is: 2026-07-11 06:07:15