Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Mouse Problems in high-res modes...
#21
Quote:Coming from someone that even got banned ~1 year ago from QB45's board when started a flame war with Blitz and me because µGL.. and that worships Future lib when even the lib's authors recommend µGL.. i'm not exactly surprised.

I bet µGL32 won't work for you either when it gets released, we will see..

haha :rotfl:. Blitz banned me out of his personal interests. And if you remember such arrogant attitudes of the admins @ qb45.com lead to its pathetic downfall :wink:

Let me ask you this question - "How many people will vouch that uGL works 100% on their computers?"

The answer - "Zero!" :rotfl:
( Remember, the authors dont count Wink )

If you show such arrogance with your products then I am sorry but you're product will never be able to flourish. You need to fix issues with it by listening to what the users have to say, not by denying that there are no issues with your product and its the perfect piece of software! BS. Any attempt to reason with you or blitz has been a waste of my time.

Oh and Allegro will beat the shit out of uGL anyday Wink
Reply
#22
TheBigBasicQ: Not hi-res/SVGA lib is even going to be 100% compatable as not all cards are. UGL has been widely recognised as the best hi-res lib available for QB. Its just not everyone uses hi-res in QB.

Becareful of calling people arrogrant when you can yourself be perceived as being it.

Comparing it to allegro is pointless as I've never seen QB program use it directly.
Reply
#23
Quote:Oh and Allegro will beat the @£^$ out of uGL anyday

Heh, how would you know that? You must be a coder/programmer/developer to compare function libraries and i don't remember seeing a single piece of code written by you - i'm sure i'm not the only one here.

If you could take the time it took to post in 1 year and half those 3600+ messages, and actually code something, lets see.. 5 minutes to read the messages and then write a reply.. 18000 minutes, ouch.. say you used those 300 hours to sit down and code.. man, i could have written a 32-bit QB-compatible compiler with that free time ;)


Quote:If you show such arrogance with your products then I am sorry but you're product will never be able to flourish. You need to fix issues with it by listening to what the users have to say, not by denying that there are no issues with your product and its the perfect piece of software! BS. Any attempt to reason with you or blitz has been a waste of my time.

"Product"? What product? uGL is a programming project, not a product. Just to remind you, it's fully open-source, and you, mr. "Linux lover", why didn't you try to help finding the bugs you mentioned (but never showed).. that's the only way any open-source project can get better, with patches sent by users (remember, this is a functions library, not a word processor). Maybe the code was too complex to you? I can understand that..

We never denied anything, the problems with ATI's and Voodoos cards (the video-cards that we really know that have problems because the users reported us exactly what was happening, instead of saying "THIS LIB IS PURE SH*T! F*CK YOU!" forgot the qb45.com's posts eh?), are well known and Blitz even made a compatible test tool, but not many helped running the test and sending the results, you can guess.. http://badlogic.bad-logic.com/index.php?...e=modes.db


I'm sure you will be the last one replying, as i already lost too much time with this and don't want to beat your ranking in number of posts (again, congrats!). Trying to explain anything related to programming to you is so hard as explaining rocket science to a 8 years old child, i give up. You won pal.. uGL sucks ass and you are the most qualified person here to say so, cheers.[/quote]
Reply
#24
Forget it v1ctor, arguing with him is like arguing with a religious fanatic. TBQ is like a old scratched record if you know what i mean. I never saw or got one intelligent reply from him. Just the same old answers. Anyways, i think we've proven many times that if you use µGL right you can get more compability then dqb. They've seen that quake renderer i did, and other stuff. That's more then enough proof.

And btw, during the 1.5 years i was admin i only banned one person. And that was you TBQ. Personal issues were never the case. It was your constant flames and swearing. You got alteast 5-6 warnings as well. Now post anything you like, i don't consider you worth my time. So i'm not going to reply.

Last thing, allegro is for protected mode dos. That means flat mode and access to 4 GB. You're comparing visual c++ and other 32 bit compilers to qb. Well that's just beyond stupid. Besides, uGL beats allegro performance wide anyday. Allegros innerloops are all written in C, and the algos aren't all that good. You can ask shawn hargrove to compare µGLs innerloop to allegros and see what he says if you don't take my word for it.
oship me and i will give you lots of guurrls and beeea
Reply
#25
Quote:man, i could have written a 32-bit QB-compatible compiler with that free time Wink
So why didnt you?

Quote:"Product"? What product? uGL is a programming project, not a product. Just to remind you, it's fully open-source, and you, mr. "Linux lover", why didn't you try to help finding the bugs you mentioned (but never showed).. that's the only way any open-source project can get better, with patches sent by users (remember, this is a functions library, not a word processor). Maybe the code was too complex to you? I can understand that..

Dont play with words. You very well know what I mean. BTW its not the job of the user to make a patch. If you know anything about bug detection and issuing patches then you should know that first the developers *must* acknowledge that the bug exist :roll: which you never did in my case.

I remember telling you that ugl would crash in the debug mode. But you guys always brushed off my post saying "It's impossible for uGL to crash in debug mode". Thats not a very positive answer from a developer, is it? :lol:

Heres a quote from this thread:

Quote:Well, it's not only UGL's mouse module... it's more. I just run one of your examples (e.g. the line-drawing one, or the one with the polygons), and it crashed. Simple as that.

Yes and now he has a bad box and his hardware is all non-vesa compliant, is it? :barf: I remember posting exactly the same problem 2 years ago on qb45.com.

Quote:We never denied anything, the problems with ATI's and Voodoos cards....

Guess what? I had 2 SiS cards which had full VESA compatibility and uGL would keep crashing Wink. Mind you that Future.Lib still works on WinXP, ME, 98 on all those cards that I listed in my previous posts. My hardware has changed from the legacy to bleeding edge :???:

Quote:....dont want to beat your ranking in number of posts (again, congrats!). Trying to explain anything related to programming to you is so hard as explaining rocket science to a 8 years old child, i give up.

pure arrogance :barf:

Quote:Anyways, i think we've proven many times that if you use µGL right you can get more compability then dqb....

yep, that means you dont know how to use your own library Wink because those examples crash :roll:

Quote:...Personal issues were never the case. It was your constant flames and swearing. You got alteast 5-6 warnings as well.

If thats the case then you should've been banned a long time ago. You were the one who started the flaming, name calling etc... I know your favorite word too Wink - "Queer" :roll:

Quote:Now post anything you like, i don't consider you worth my time. So i'm not going to reply.

Thats what you say in all your replies Wink

Quote:Last thing, allegro is for protected mode dos. That means flat mode and access to 4 GB. You're comparing visual c++ and other 32 bit compilers to qb. Well that's just beyond stupid. Besides, uGL beats allegro performance wide anyday. Allegros innerloops are all written in C, and the algos aren't all that good. You can ask shawn hargrove to compare µGLs innerloop to allegros and see what he says if you don't take my word for it.

:rotfl: rotflmao. I wasnt comparing Allegro to UGL (DOS). I was talking about the 'to-be' Win32 version of UGL. This is a written proof of how incompetent you think others are :rotfl:

PS: I thought you had left Qbasicnews because "you had enough of us". :rotfl:
Reply
#26
Quote:v3cz0r wrote: man, i could have written a 32-bit QB-compatible compiler with that free time

Quote:So why didnt you?

Heh, wait some weeks and see.. i won't tell you anything about it now, sorry, it's just for coders ;)


Quote:Guess what? I had 2 SiS cards which had full VESA compatibility ...

SiS had(still has?) one of the most f*cked VESA BIOS ever written, i had to trace inside of my SiS 620 using SoftICE for DOS 'coz uGL was crashing for no reason, and guess what.. it WASN'T uGL's fault, but the BIOS service WASN'T preserving the registers it SHOULD. Using flib or running a pmode DOS game wouldn't show any problem, as the problem would ONLY happen when certain STANDARD VBE services were called from real-mode. Guess why uGL uses those STANDARD services.. for getting more speed, so users could make BETTER/BIGGER games, that's what we had in mind when we started writing the lib.


Quote:Yes and now he has a bad box and his hardware is all non-vesa compliant, is it? I remember posting exactly the same problem 2 years ago on qb45.com.

Just saying it's crashing helps alot, sure.. Again, lets try to explain open-source to non-coders:

If an user posts a report with ENOUGH information to the point that the bug can be REPRODUCED on the developers' boxes, then, if no developer from that project helps fixing the bug coz he/she doesn't want/care, nor any user can find the real cause themselves, you can call the project maintainers (or the project itself) anything you want (stills, if you can't do better or help, you could just stfu). Now, if the user just complains saying it's crap or whatever (as you did at qb45.com's board), then, mate, forget any kind of support, no developer from any open-source project would do anything ever. Want to complain like a baby and yet have all your problems fixed? Pay for it and wait, simple as that.


Now.. back to the work.. FB is coming babe, whoo ;)[/quote]
Reply
#27
Quote:SiS had(still has?) one of the most f*cked VESA BIOS ever written, i had to trace inside of my SiS 620 using SoftICE for DOS 'coz uGL was crashing for no reason, and guess what.. it WASN'T uGL's fault, but the BIOS service WASN'T preserving the registers it SHOULD. Using flib or running a pmode DOS game wouldn't show any problem, as the problem would ONLY happen when certain STANDARD VBE services were called from real-mode. Guess why uGL uses those STANDARD services.. for getting more speed, so users could make BETTER/BIGGER games, that's what we had in mind when we started writing the lib.

Yes, it was a good aim but unfortunately it doesnt work. What good is a porche 911 without any wheels :rotfl:.

Answer this question - "How many bigger and better games have been written *with* UGL and they work for most people?"


Quote:Just saying it's crashing helps alot, sure..

What more information do you need? You have the card's specs(manufacturer. model), the symptom(crashing), the code(UGL examples...). :roll:

Quote:...as i already lost too much time with this and don't want to beat your ranking in number of posts (again, congrats!).
I thought you werent gonna waste anymore of your 'precious' time.
Reply
#28
Quote:
Quote:Just saying it's crashing helps alot, sure..

What more information do you need? You have the card's specs(manufacturer. model), the symptom(crashing), the code(UGL examples...). :roll:

He means generally, not this particular case. :roll:

Quote:Yes, it was a good aim but unfortunately it doesnt work. What good is a porche 911 without any wheels :rotfl:.

You need a driving license before you should be let anywhere near a porsche. :wink:
8% of the teenage population smokes or has smoked pot. If you're one of the 2% who hasn't, copy and paste this in your signature.
Reply
#29
Quote:
v3cz0r Wrote:SiS had(still has?) one of the most f*cked VESA BIOS ever written, i had to trace inside of my SiS 620 using SoftICE for DOS 'coz uGL was crashing for no reason, and guess what.. it WASN'T uGL's fault, but the BIOS service WASN'T preserving the registers it SHOULD. Using flib or running a pmode DOS game wouldn't show any problem, as the problem would ONLY happen when certain STANDARD VBE services were called from real-mode. Guess why uGL uses those STANDARD services.. for getting more speed, so users could make BETTER/BIGGER games, that's what we had in mind when we started writing the lib.

Yes, it was a good aim but unfortunately it doesnt work. What good is a porche 911 without any wheels :rotfl:.

Answer this question - "How many bigger and better games have been written *with* UGL and they work for most people?"

Hey, I try.

If I could only learn to finish stuff, make backups and keep my code legible...

--j_k
size=9]"To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public." -- Theodore Roosevelt[/size]
Reply
#30
Quote:What more information do you need? You have the card's specs(manufacturer. model), the symptom(crashing), the code(UGL examples...).

Heh, that sounds like a grandmother calling M$'s help-desk for support.. "alright, first, close all windows.. ok, wait.. (2 minutes later) hello? (more 5 minutes of total silence) ok back, it's done, what next.. no madam, i meant the windows in your desktop, not the real ones".

But i understand you, i would feel somehow frustrated being in a community where i don't belong.. piss everyone else would be my favorite game, along saying how great i were and how much everyone else sucks.. it's way easier to do and much more fun than coding,for sure ;)
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)