Scott, I had asked about a topic offline, and it sounded like there was no compiled resource at Autodesk, so it seems like it has to be compiled "from the trenches" as it where. And that topic being, documentation of the Revit.ini file. Many offices edit the OOTB ini every year, others keep reusing their old office standard ini. In either case, there are all sorts of keys that are either not in the OOTB version, but can be really useful to add (killing the graphics card warnings, for example) while others are now deprecated and perhaps better to remove, such as some of the Performance Optimizations. It would be nice to have a master list of all possible ini keys, what versions of Revit they apply to, and what effect they have. Some of the stuff I am trying to address prior to 2012 rollout includes...

[Messages]
SuppressHardwareFullySupportNewDriverWarning=1
SuppressHardwareFullySupportOldDriverWarning=1
There is a third one I think for "driver too new". Anything else?

SPLWCount=0 What does this do?

[PerformanceOptimizations]
I am pretty sure the old ones for ParallelWallJoins and ParallelPrintProcessing are handled automatically now. But is there anything new here?

Stuff that focuses on install and configuration seems really timely.
Oh, and :beer: for taking this on. In order for wikihelp to take off it needs to be really useful, and focusing on the content that actual users need right now will make it a lot more useful. Waiting a month to "see how things go" will mean our first impression is not as good as it could have been, which is hard to claw back from.

Gordon

Since I have this shiny new 2012 software, I would like to know the practical applications of the "Parts" workflow. I looked in the help file, but it only gives me written how-to instructions with no real world context. So this is how you create a part, this is how you divide a part, this is how you edit a division of a part - but what are parts actually useful for? What's in it for me? There is a short video that plays when I hover over the button on the ribbon that does not help much.

There are no relevant videos or skill-builders that I can find. The eLearning section on my subscription page for RAC stops at RAC 2010.

I have a storyboard for a video on the parts functionality on my desk right now. Stay tuned for additional information on the parts functionality.

The tool is primarily intended to help with construction sequencing and materials take offs. Allowing the model elements to be broken down into discreet parts and then furhter divided supports a better workflow for using the Revit model for construction.

ADMIN NOTE:
This thread has been split. Please use this thread for the original intent: "Please respond with the areas/topics in help that seem to need the most....attention"

The new thread can be used for general discussions about the Wiki...

Gordon (et al.)

I have started a section under tips and tricks titled The Revit.INI file. I will be detailing each section, and providing info where I can. I encourage each of you to help contribute to this section as well! It's still currently in "Draft" mode, going through the internal review process, but it should be "approved" sometime today and go live. It's the basics at this point, and meant as a placeholder for further development. Thanks for suggesting it!

Scott
Thanks for the ini stuff. If there are specific lines in the INI that we would like to see explained, do we post there as a comment, or here? Knowing what all the INI options are is the first step, knowing what they actually do is the next, Many are self evident, but many are not.

And I will post another wish that I think would be hugely helpful, and easier for you to get via access to Factory brains for picking. To wit...
Documentation of Warnings! It would be great to have a list of all the warnings that are possible, with an urgency level, say "Must fix". "Gray Area" and "OK to Ignore". Maybe this data would then help get the Warnings dialog updated, with the urgent stuff in red, ignorable stuff green, etc.

Thanks!
Gordon

Best place to get this information is by posting comments to the topic in the wiki. This WILL be seen by multiple moderators of the wiki and they will act on it in some way. They might not have the information directly but it will trigger off at least a reply back to the comment and perhaps a search for the information or a request to a few developers/QA who can help provide additional information.

Posting the request for additional information here only gets a couple of factory eyes on it and we are not held to ANY kind of response SLA (service level agreement) on posts to this forum. Most of us use this forum on our own time. :-)

Well Jeff, given that what I posted originally was a request for explanation of those items, I don't really see why I should have to do it again. Unless of course the goal is just to drive the appearance of traffic at wikihelp? I was hoping to see something useful, and made an effort to see that happen. It didn't, I got a useless copy on an INI with no info about what anything does. Do you REALLY think that helped anyone?
And really, SLA? Have you tried to use subscription help lately? That we as customers actually pay for? Yeah, wikihelp is sure to be so much more responsive. I'll put my eggs in the RFO basket, thank's very much. The wikihelp basket looks to be made of wet paper.

best of luck,
Gordon

Sorry you feel that way.

I am not really sure why you asked the question in the first place based on your response to my answer. If you never intended to post a comment to the wiki then why ask Scott:

I guess it was a retorical question

One sure way to NOT get what you want out of the wiki is to not participate. I am trying my best to communicate to you the best chance you have at getting what you want. The wiki is seen by many more people at Autodesk who are supposed to respond to users and make it a better experience. The stuff posted here does not get the same level of attention.

You can ask Scott what his thinking was on the posting of the INI file and why he did not address your specific questions with his posting. He is the one who made that entry.