CompuServe Messages

#Imagine 3.0, uhhh…

    21-Nov-93 20:24:46
Fm: Mike Halvorson 74250,774
To: jeff Holinski 71172,1417
I guess this is my last response to your comments. So far all you have done is tell me of other software not make suggestions of what you would like to see. Be creative, dont suggest that we copy the hard work of another vendor. You would find problems with that if we copied someone elses code. Imagine has been invented by users who have had an open mind and a clear vision of what they would like to see. We have thousands of letters which out line in great detail what they want to see. Not any of these letters suggest that we copy something from some one else. We have noticed that many things done in different code ends up being the same or very close. If you have a suggestion, think it through and then react with a real suggestion, written down, with pictures so that we can evaluate what you want. I am not here to debate with you or anyone else this train of dialogue that you desperatly want to establish. I invite you to call me, at my expense, 1 800 328 0184 and we can to your hearts content, debate what ever you want, providing I have the time, which if I have it I will take. I am here to help users who have questions about the software and hardware we make, NOT to carry on with someone who seems bent of having an argument. So, jeff, if you want to participate in this dialogue I have given you the frame work from which I can and will work. Comit your ideas to paper, put your ideas where you mouth seems to be. I will be glad to review any and all suggestions that YOU make, however simply saying, Hey these guys did it this way and so should you, does not carry any weight with me or the developer staff. As for breaking the textures from Apex. Here is the deal, we write Imagine, not textures from Apex. In order to do Kinematics and other features, we had to change the object format. Also we have improved the texture code by making them tackable. So I guess you dont want texture tacking, like everyone else. We should in this case not put in something the user base has asked for. Apex will have to adjust their code, and maybe this time instead of reverse engineering the code they can call us and we will be glad to tell them how to avoid this problem in the future. jeff, you are one angry person, and for no reason that I can figure out. Like I said, take a breath. Remember, I have no intention of spending anymore time with this line of conversation, other people have suggestions and complaints that need attending to. I look forward to YOUR suggestions and bug reports if you find them. Nuff said. Mike