• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Article titles

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,342
Country
netherlands
Paul,

I think we should discuss how to use the article titles, before we continue renaming a lot of articles. I don't think all of the new names make things easier to find.

For example: "Modeling - Tweaks - Applying (ASM)"

This is not clear at all. First it is not related to modelling necessary, it is a general introduction to using the ASM files for scenery design.

Besides that my idea was to have the general scenery design template to do part of this structuring. I don't think we should put the structure of the Wiki too much in the article titles.

So for the ASM tweaking example again, in the scenery design template that was one of the main headers, with the related tweaks articles listed under it. That makes it easier to navigate between them. But it does not make sense at all to let them all start with "Modelling - Tweaking - ...".

It would be similar to let all history related articles on Wikipedia start with "History - ...". In my opinion it does not make things clearer. But I would like to hear other opinions on that.
 
Hi Folks

Please do not respond yet.
I'll complete this info tomorrow.
Been up since 04:30. :D

Additionally -
Any doc, currently accessed via an interim redirection,
will be directly linked,
as soon as that child doc name is finally agreed.



Arno -
I fully appreciate the creative work
& issues resulting from the organic growth of this wiki.
I'm just trying to rationalise the content from a user POV.



I don't think all of the new names make things easier to find.

For example: "Modeling - Tweaks - Applying (ASM)"
I fully agree.
ASM tweaking moved to Modeling - Tweaks - Applying (ASM)
RefPoint parameter performance influences moved to Modeling - Performance Influences - RefPoint Parameter

With the above two ASM related re-titlings,
my enthusiasm overstepped my knowledge. :o



However,
for the remaining > 50 re-titlings
I do think those are appropriate,
as is the underlying nomenclature/taxonomy. :D



Document titling should be rational
and specifically indicate their context & content.

Naming must also account for contextually related topics.



Again I acknowledge the issues resulting from the organic growth of this wiki.

The old titles were conversational,
non user friendly,
and certainly non-compliant with wiki standards. :duck:

The root of the 'conversational' problem
lies with -
- there being no naming guidelines
- yyy
- creators naming linked docs
in the context of the paragraph text in the parent topic.
- creators not using [[doc proper title | doc contextual title]]
- xxxx



Note -
I've grouped the 'move log' pages by subject,
so you're seeing these more clearly
than any user would ever have done in their category presetations. :D

I've also concatenated any multiple changes,
into -
ORIGINAL NAME moved to FINAL NAME

Key for below -
OLD TITLE moved to NEW TITLE - COMMENTS



e.g. of conversational titles -
Scenery Design Tools moved to Tools - Scenery Design - To match future'Tools - Aircraft Design' topic rtc.



Taxilines with Gmax moved to Ground Polygons - Taxilines (GMax)
Ground polygons with GMax moved to Ground Polygons - Applying (Gmax)
Ground polygons with Gmax - How to create the polygons moved to Ground Polygons - Creation (Gmax)
SCASM How to fix ground polygon bleed through moved to Ground Polygons - Issues - Bleed Through (SCASM)



No shadow moved to Modeling - Tweaks - No Shadow
Exporting from 3D Studio Max moved to Modeling - Exporting (3DSMax)
LOD models moved to Modeling - LODs
Simple GMAX building texturing video tutorial moved to Modeling - Buildings - Texturing - Tutorial Video (GMax)
Gmax model guide moved to Modeling - Intro Guide - 1 (GMax)
Gmax model guide details moved to Modeling - Intro Guide - 2 (GMax)
Build your own house moved to Modeling - Buildings - Make your own house
Basic GMax tweaks moved to Modeling - Tweaks - Basic (GMax)
Manifold Geometry moved to Modeling - Manifold Geometry
Saving X files using MDLCommander moved to Modeling - X Files - Saving With MDLCommander
Gmax for FsX moved to GMax (FSX)

Modelling and texturing for performance moved to Modeling and Texturing - Optimising for performance



Library creation for FsX moved to Library - Creation (FSX)
Making a library without FsRegen moved to Library - Creation - Without FsRegen



SCASM Conditional display moved to Conditional Display (SCASM) - To match existing 'Conditional Display' topic



SCASM Effect placement moved to Effect - Placement (SCASM)
Increasing the effects view distance in Flight Simulator moved to Effect - Visibility - Distance - Increasing



How to Create a PAPI-4 Approach Lighting System moved to Lighting - Approach - PAPI-4 - Creation
Lights, what they can and can't do moved to Lighting - What Lights Can And Can't Do
Apron lighting with effects and XML moved to Lighting - Apron - Using Effects And XML
Using GMAX to Create Apron Lighting using Effects moved to Lighting - Apron - Using Effects And GMax



Texture Formats (Overview) moved to Texture - Formats (Overview)
Reflection and scenery moved to Texture - Reflection And Scenery
Correcting perspective with the GIMP moved to Texture - Perspective - Correcting with the GIMP
Seasonal textures moved to Texture - Seasonal
Disappearing textures moved to Texture - Disappearing
Creating night textures moved to Texture - Night
Transparency problems moved to Texture - Transparency - Problem solving
Using the alpha channel to create transparant textures with PhotoShop moved to Texture - Transparency - Alpha channel - PhotoShop
Missing Textures (FSX) moved to Texture - Missing (FSX)
Texture.cfg - FSX moved to Texture.cfg (FSX)



Rotate with wind moved to Animation - Rotate With Wind Direction
Animating doors in FSDS Version 3.x moved to Animation - Doors (FSDS 3.x)
Frequency controlled animations moved to Animation - Frequency Controlled
Rotate to user moved to Animation - Rotate To User
Animations explained moved to Animation - Explained
Gate animation tutorial moved to Animation - Gates - Tutorial




Function Reference moved to Missions - Function Reference
Mission Creation moved to Missions - Creation
Tools moved to Mission - Tools



Airport elevation change in FS X moved to Airports - Elevation - Modifying (FSX)
Structure of Airport files in FSX moved to Airports - File structure (FSX)


Working with FwTools and GeoTIFF files moved to GeoTIFF files - FwTools - Working with
Accessing SimConnect From VB moved to SimConnect - Accessing from VB



FsX MDL format moved to MDL format (FSX)
Change cameras views moved to Cameras Views - Changing
Using Marker States moved to Marker States
Object Placement Tool moved to Object Placement Tool (FSX)
FSX Problem Resolving moved to Problem Resolving (FSX)



HTH
ATB
Paul
 
Last edited:
Hi!
Document titling should be rational
and specifically indicate their context & content.

Naming must also account for contextually related topics.

The old titles were conversational,
non user friendly,
and certainly non-compliant with wiki standards. :duck:

The root of the 'conversational' problem
lies with -
- there being no naming guidelines
- yyy
- creators naming linked docs
in the context of the paragraph text in the parent topic.
- creators not using [[doc proper title | doc contextual title]]
- xxxx

As the post indicates, we do need guidelines.

If guidelines are written, don't forget the language barrier. Many (most?) of the forum members don't have english as their mother tongue. So it's important the guidelines are written in a simple to understand english.

For example the quoted text says "[[doc proper title | doc contextual title]]"
What is a proper title?
What is a contextual title?

The guidelines needs easy to understand examples of "correct" naming.
 
Hi guys,

I agree we need guidelines, after my moving I should work on them. Until that I would suggest to stop this kind of changes for a while.

While a lot of the moves you made Paul indeed make it clearer, I still think that adding things like "Modeling -" in the title is not a good idea. In that case we need a Modeling category How subjects are grouped in categories should not be in the title IMHO. For that we have the categories and maybe we need to make some "entrance" pages for common activities like Modeling, Texturing, etc so that users can find an entrance point for the articles they are looking for.
 
Back
Top