From: Charles Boardman To: ml@qoole.com In-Reply-To: <003101bd45fc$40916ef0$0b64a8c0@piraino.eyecom.com> from "John Piraino" at Mar 2, 98 10:57:05 am Reply-To: ml@qoole.com Date: Mon, 2 Mar 1998 18:00:00 +0000 (GMT) Subject: Re: Amazing Sorry Mr Piriano, can't let this one go anymore without comment. > I find it amazing and amusing how much inferiority people will put up with. *snip* > 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. What you have to remember sir, is that there are a great deal of satisfied Qoole customers out there. I think that it is very sad that you are having such problems with Qoole, because I can't say that I share your bad experiences. > 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. Well, again this all stems from your unfortunate experience with Qoole. Matt and Paul at Lithium Software have an extremely good and positive attitude to their users, and I find respond very well to any problems that are raised. Why, only yesterday I popped into #qoole on efnet and there was Mr. Matt Ayres busily helping lots of ppl out, yet still finding the time to chat with me and discuss a few things. Thanks for that Matt, by the way. I am curious though, Matt replied to your e-mail demanding your money back saying okay, get in touch with their sales department and you can. Are you going to remove Qoole from your hard drive? 'Cos you'll be faced with the situation where you are being reimbursed for something that you already have. I hope you are honest enough to not carry on using the registered version of Qoole once you have your refund. Don't think for one minute that I am implying you might do otherwise. I'm just telling you it may look like you are getting something for nothing to a by-stander. > 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! Calling people idiots isn't very constructive Goldeneye. Why not just settle for thinking 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. With respect, the version of QBSP that you use can be significant. Just 'cos they are the ones on the Lithium site, it doesn't mean they are the best to use. They are just something to get you started. I wonder perhaps if you expect everything to be handed to you on a plate. A level that compiled fine with the version of QBSP from Lithium sites did not compile with the QBSP that I use now (which is far superior). Tell you what though, it most definitely can be a problem with the QBSP you use at times (although I understand and agree that this is not the case for you in the situation that you stated), as one level I had compiled fine with one QBSP I had, but you could fall through bits of it when it was compiled with the other QBSP. Weird or what? > 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...") Yeah, well, this problem has hopefully been fixed now. Its been addressed in the latest release of Qoole, and hopefully is fine now. This is what I was talking about though when I said how good support was from Matt and Paul. You tell 'em about a bug, they prioritise (spelling?) it, and then they fix it according to priority. I may have been the one that pointed out that this was that floating point/ level deterioration problem. I had it happen to me on my last level, but because I kept on top of my level (in full control of design, structure etc) I found the leak in like two minutes amd fixed it in the next two. But hey, this problem should never happen again :) > 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, cut node portal is not an error. Its a warning and I've never come across a situation where it stops a map from compiling and running properly. > 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. Your problems seem to revolve around this level deterioration problem. You don't seem to mention any other bugs with Qoole that were of major concern to you. Just this one. Now that it has been fixed in the latest release, what is your attitude towards Qoole now? Is it still a crap piece of software that doesn't do what it is supposed to (in your humble opinion, of course)? > 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. Well, this is where I disagree with you. I don't regard Qoole as a "faulty" product, because its always under development and being improved. I hope you can find the patience to use Qoole a bit more, 'cos that's all it takes, same as most things in life. I would gladly have paid double for Qoole than what I did if I had known just how good the support was for it, and just how much progress it was going to continue to make. Best of luck to you whatever you decide upon, MoonGlum. ---------------------------------------- Charlie Boardman :: chb96r@ecs.soton.ac.uk ICQ UIN (MoonGlum) :: 2275190 www.dsse.ecs.soton.ac.uk/~chb96r/moonglum.html -------------------Here endeth the email.-------------------