From: "Julian Easterling" <jeasterling@pascal.coker.edu>
To: <ml@qoole.com>
In-Reply-To: <003101bd45fc$40916ef0$0b64a8c0@piraino.eyecom.com>
Reply-To: ml@qoole.com
Date: Mon, 2 Mar 1998 13:15:27 -0500
Subject: RE: Amazing

I think that the problem you are describing has to do with the floating
point map coordinates stored in QLE format.  I have noticed that other
people have had the problem you describe when Qoole converts QLE to MAP. MAP
formats don't allow Floating point.  It may be that Qoole rounds these
number off.  For instance (using 1D for example), If you have a brush that
ends at 345.4999 and another brush that starts at 345.5000, When Qoole
converts to MAP your first brush ends at 345 and your second brush starts at
346, thereby creating a 1 unit "hole" in your map.  If that brush is on the
outside of your map, It just created a leak.
This drives me up the wall too, but I have heard that this problem is
suppose to be fixed in the 2.33 version of the program. I am not sure about
that though.  It makes me curious to know if this is an advantage(using
Floating Point) when none of the tools(BSP,VIS,LIGHT,RAD) use them.  I would
suggest that it causes more problems than it is worth then it should be
deleted or give the user the ability to turn it off if the problem can not
be fixed.
I have looked at other editors and while they have there own problems, they
are much more complicated to use.  As long as we keep reporting the bugs we
find and the authors keep fixing them, I am going to stay happy with the
product.  Just about every program out there has problems.  Sometimes by
adding new features(which are better) you create problem(bugs) trying to
interface them with older programs.
As far as I concerned, the authors are doing a good job of keeping new
features coming and getting rid of old bugs in each release.  Maybe I am
forgiving, maybe I am idiot, but I am happy with Qoole.  Just look at the
windows platform, it has a lot of bugs in it but people continue to use it.
Each time Microsoft adds new features to the OS, new bugs appear because the
older programs weren't designed to work with the new feature. Take FAT32 for
example. Take Long Filenames for another.
This is not intended as a flame but to give insight to your problem since
everyone(for lack of a better word) seems to want to name call. I hope this
helps your problem.

Julian.

--------------------------------------------
Julian Easterling, Lab Manager
Coker College  Hartsville,SC USA
Email: jeasterling@pascal.coker.edu

A Person is only as big as the dreams he dares to live!

-----Original Message-----
From: owner-qoole@qoole.com [mailto:owner-qoole@qoole.com]On Behalf Of
John Piraino
Sent: Monday, March 02, 1998 11:57 AM
To: ml@qoole.com
Subject: Amazing


I find it amazing and amusing how much inferiority people will put up with.

John M. Sanderbeck writes:
Why don't you post this message to the Qoole Programmers, not to the Mailing
List. I'm tired of reading your whining messages.  If you don't like Qoole,
then QUIT USING IT....   I have minor problems with the software, but you
don't hear me on here WHINING!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!   For
Christ's Sake, get a life....   And, I am a programmer and have been for 10
years, so don't give me the bug free software line of bull...  There is no
such thing......

Mr. Sanderbeck, I would have a life and I wouldn't be wining if I purchased
a product that does what it is supposed to do.  WinQoole/GLQoole does NOT do
what it is supposed to do.  It does not save QLE files correctly or build
MAP files correctly in order for the tools from id to do their job properly.

Secondly, if this is the kind of software that you are happy with, please
keep spending.  If you are a programmer for more than 10 years, you should
be grateful to God that you don't work for me.  (Director of MIS responsible
for 72 programmers).  If this is your attitude, and your thoughts on
producing software, you would be unemployed.  I'll gladly keep your name on
file in case I ever see your resume cross my desk.

Goldeneye007  writes:
Ok,first of all idiot,your so stupid you don't even know it!No matter what
kind of software you use it will always have SOME kind of bugs that are
infixable because the programming would cause more complications then it
would help.Second the Qoole programmers did no even make the qrad,qvis,and
qbsp ID software did som dont be blaming it on them!Why don't you just
return the damn thing if you don't like it!

If Qoole has a software bug that makes it infixable, then the entire project
should be scrapped, as the software doesn't work from the start.  I see, you
are like Mr. Sanderbeck who doesn't mind spending money for things that
don't work.  You must be really ignorant if you thought that I felt QBSP,
LIGHT and VIS came from Lithium.  I wasn't born yesterday.

Secondly, the bug is NOT in WQBSP, QBSP256 or QBSP (I try them all) the
problem is in the creation of the MAP file (If you were to read the message
properly before flaming)

As I explained, I had deleted a room that I had created over 5 days ago.  I
haven't even been working on that part of the map, and all of a sudden
there's a leak.  I don't think that's id's tools, that's the creation of the
MAP file, which WinQoole does.  (Watch the screen the next time you Export
to BSP, you'll see a message box stating "Exporting map file...")

As stated in the letter that I have found the problem, it is in the saving
or re-loading of QLE files.  If I can have a part of a map untouched for 5
days, and then have it come up with a leak and a cut node portal error,
that's not QBSP!  If it was, it would have found that 5 days ago.  I found
this by deleting one room at a time, and then covering up the hole with a
solid cube.  Once I found the offending room, I replaced it with another
room the same size, texture, etc.  Then it worked fine again.

It appears that everyone is defending their "faulty" purchase, as no one
likes to buy a "lemon".  If you want to spend your money fiverously, I have
a bridge that I've been wanting to sell for a few months now.

John




