CompuServe Thread

#Message Sections

18 messages in this thread
#87732From: Brian Rudolph [Adesk]Mar 1, 1994 6:15 PM
For everyones information: Because of the increased traffic on the ASOFT forum, to make things easier for our members we are considering making some changes to some of the message sections. We feel the forum will greatly benefit from these changes. We are planning on splitting up the 3D Studio section into 2 sections, one dealing with 3DS Modeling/materials and one dealing with 3DS animation. Also we are planning on splitting up the IPAS/POCO/AAWIN section into two sections. One section would deal strictly with IPAS usage, and would provide a place for IPAS developers to support their products on the forum. The second section would be for software developers using IPAS and other SDK's. This section would deal only with developer's issues. We feel these changes will benefit the forum members, and hope the the transition process not cause confusion or inconvenience. We will post a message detailing exactly what will be changing and when it is to change later in the week. P.S. Please do not reply to me PRIVATELY as I will be out of the office and will not get your e-mail. If you wish to privately respond to this e-mail please address it to either Jonas Ruikis or Nik Grant. These other two SYSOPS will be happy to address any concerns. Any FORUM (public) replies to me will be read and answered by one of the other ASOFT SYSOPS. Thank you.
#87742From: John EllisMar 1, 1994 7:00 PM
At the risk of starting another "Tempest in a Teapot" (Earl Grey's, Gary favorite. <g> ) I am curious to know why Modeling/Materials would be split up from Animation? It seems to me that a more logical division would be hardware and software as these two areas encompass at least 70% of the message threads. I think a specific section for development of IPAS and answering IPAS related questions makes sense. If it is it being suggested that you'll have to log into these different areas specifically, I for one would find this very awkward. If that is the case then a seperate section for developers would work, but breaking the rest of the forum up between Modeling/Materials and Animation doesn't make any sense to me. And as there is no mention of hardware, I wonder what's going to happen to that? I would like to propose the following if my impression is correct that you want to create 4 different sections. 1) For IPAS developement and questions. 2) 3DS Animation, Materials and Modeling 3) Hardware related issues. Unfortuneately, I think breaking up the forum like this will compartmentalize the overall free flow of discussion. IMHO. Wouldn't it be better to keep it all in the same place and have a specific Sysop responsible for each one of the 3 divisions? John (In the Eye of the Hurricane) Ellis P.S. Anyone for a cup of Tea before we discuss this? <g>
#87768From: Gus GrubbaMar 1, 1994 8:42 PM
I think it's overall ok. My only objection is in dividing 3D Studio that way. I would divide in: "How do I do this?" and "I can't get this thing to work"…
#87794From: John TissavaryMar 1, 1994 9:38 PM
Good suggestion, Gus. John Tissavary (La Luna cie)
#87798From: Yost GroupMar 1, 1994 10:25 PM
I like John Ellis' suggestion of breaking out the hardware questions. That way Gary and I could avoid that section entirely. <g> – Jack
#87784From: John TissavaryMar 1, 1994 9:08 PM
This seems like a really useless division of the 3DS forum. I can fully understand wanting to keep the section traffic manageable, but my feeling is that this won't do it. I really don't notice many messages that divide modeling/mapping and animation. I think the biggest traffic jams are hardware messages being posted in the 3DS section. Perhaps sysop's monitoring of hardware threads and placing them in the Hardware section would help more. John Tissavary (La Luna cie)
#87804From: David J. MarksMar 1, 1994 10:32 PM
>> 3DS Modeling/materials…and 3DS animation. There's a fine line there. It may be more effective to split it into 3DS Installation/Hardware Issues and 3DS Techniques.
#87816From: David StinnettMar 1, 1994 11:48 PM
To the powers that be, I agree with the others that an installation/hardware/tech ("when I use my so&so video card I get this error in the mat editor…"), and a general/how-to/tips ("I'm trying to get a copy of this object to move along this path….") section is a much more logical and useful division of the 3ds section than the proposed modelling and animation split. Please consider it. Thanks. David
#87823From: Yost GroupMar 2, 1994 12:31 AM
It would be helpful if you could explain what the specific rationale for wanting to split up 3DS questions into modeling and animation is. ?? – G
#87855From: MARTIN G FOSTERMar 2, 1994 5:16 AM
Brian, >> We are planning on splitting up the 3D Studio section into 2 sections, one dealing with 3DS Modeling/materials and one dealing with 3DS animation. << Bogus. I agree that a better split would be into "3ds: installation/ hardware issues" and "3ds: how to do?" would be far more logical.
#87876From: ALAN IGLESIASMar 2, 1994 8:57 AM
I agree TOTALLY with you, Martin. Adesk guys– if yer gonna split things up, please do it this way! -Alan
#88166From: Don LandisMar 2, 1994 9:42 PM
I agree too with the split of software/hardware. Makes sense, common sense! Do you guys have this? Of course you do! We already have a hardware section. Just to be different, How about an installation vs. operation and techniques section. Many times I wish I could just download the new ideas stuff people come up with and not have to read through all the install problems many like myself have had because we just don't read the manual. <GR&D>
#88204From: ALAN IGLESIASMar 3, 1994 1:29 AM
<g> -Alan
#87874From: Bruce MeikleMar 2, 1994 8:44 AM
>> We are planning on splitting up the 3D Studio section into 2 sections, one dealing with 3DS Modeling/materials and one dealing with 3DS animation. << I agree with the others about splitting it based on Hardware vs Technique, however as a note of support for your suggestion, there is a lot of traffic specific to VTR controllers, for example. If you don't have one (and given their price, many don't), it's a waste when you DL a 20 message thread about it because the subject was not obvious and it's all useless to you. Perhaps you should split it into "3DS users with $" and "3DS users without $" <g> Bruce Meikle
#87894From: John EllisMar 2, 1994 9:51 AM
Bruce, >> however as a note of support for your suggestion, there is a lot of traffic specific to VTR controllers…. it's a waste when you DL a 20 message thread about it because the subject was not obvious. << I'm not sure how the proposed forum is going to help you on this. Typically hardware questions are in the hardware section. Just out of curiousity what software are you using to communicate with ASOFT? Some of us here are on the forum 4 or 5 times a day, but if you go with the standard rate and scan messages once a day, the cost is typically less than 50 cents a day. Even if you read everything once a day its about $30 a month with a program like Tapcis on WinCIS. If you consider that a lot I wonder how you could afford 3DS in the first place. -JE
#88137From: ROBERT RITGERMar 2, 1994 8:39 PM
John: FWIW I just downloaded GoCIS. WinCIS is now officially dead and has become GoCIS. I have not gotten the damn thing to function at all yet so I am keeping my WinCIS alive until I can get the support guys to help me out. I found WinCIS to be a very economical and feature filled program so I'll put in the effort to get GoCIS up and running. Bob
#88218From: John EllisMar 3, 1994 3:02 AM
Robert, Thanks for the update. All these programs seem a little querky in one way or another. I checked out NavCIS and went back to Tapcis. I'm sure there's something better but it works for me. Let me know what you think of GoCIS once you get it working. If it sounds good, I'll check it out. -JE
#87915From: Jim LammersMar 2, 1994 11:10 AM
>> 3DS Modeling/materials…and 3DS animation. >>There's a fine line there. It may be more effective to split it into 3DS >>Installation/Hardware Issues and 3DS Techniques. I'd second that! There's so much blab about how this or that doesn't work/won't install/invalid normal array, I get tired of wading through it. I'd love to get that stuff into a separate conference. It'd save me loads of time downloading all those messages.