I thought it might be a good idea to start a AVSIM Prepar3D Guide discussion topic in which you can post questions, remarks, tips, etc. concerning the guide.

 

I also thought about this because I had a question about the calibration information. I noticed it is adviced to set the null zone to the lowest setting 1. Now when I do this for my joystick my yoke moves almost all the time, specially to the right. To get rid of this I had to set the null zone to 25 (!). I wonder if I should recalibrate with the null zone at 25...? Or should you always recalibrate with the null zone at 1 and then change settings to whatever is needed to prevent pulling? Does it make a difference to callibarion if you set the null zone to something different? As it is now the guide seems to say a null zone of 1 is the best but I wonder if that is so.

 

BTW If the mods and/or Rob think it is better to NOT have one big guide topic, please feel free to close this one! Take note that this topic shouldn't be about assistance, support and help for P3D in general (in that case this topic could replace the entire forum in the end :wink: ) but for talking about specific P3D guide topics with the goal to help Rob to make the guide even better than it is already. So my null zone question above is not mainly about getting an answer but to make the information in the guide more clear. If you know what I mean.  :wink: I have no problems with callibration but some users may get into problems if they stick to a null zone of 1 because the guide says so.

 

Obviously this topic can also be used to point Rob to little typing errors or things like that. Not that I found any but well, I just want to make clear what the intention of this topic is.  :wink:

+1

Simplifying the null zone information for a regular experience is pretty fair, what can you do? The guide is very good and rather nicely lays out several important paths for further study. Remember it can't cover all aspects of each subject and will always lack some detail that may be important to another.

In the section dealing with Simconnect.xml  it may be worth adding that you can also use your machines name rather than the IP address, this is a much simpler method than using the IP address which can change if using DHCP

 

<SimBase.Document Type="SimConnect" version="1,0">
  <Descr>SimConnect</Descr>
  <Filename>SimConnect.xml</Filename>
  <Disabled>False</Disabled>
  <SimConnect.Comm>
    <Disabled>False</Disabled>
    <Protocol>IPv4</Protocol>
    <Scope>global</Scope>
    <Address>desktop</Address>
    <MaxClients>64</MaxClients>
    <Port>6811</Port>
    <MaxRecvSize>4096</MaxRecvSize>
    <DisableNagle>False</DisableNagle>
  </SimConnect.Comm>
  <SimConnect.Comm>
    <Disabled>False</Disabled>
    <Protocol>Auto</Protocol>
    <Scope>Global</Scope>
  </SimConnect.Comm>

 

Thanks Glynn, good to know, still learning something new every day.

 

Kind regards, Michael

I would add that using the device name requires DNS be intact. These days that's most likely all of the time but it is a possible source of problems. Start out by using the IP addresses, and when all is working change to the device names before retesting.

 

With networking addons it's easiest if the same logon credentials are used on each PC, make the Profile name and password the same on each.

 

When logging onto Windows we become members of the Users group. When making a folder to install applications onto, remember that these belong to the user that created the folder, not anyone else. To ensure no snags in future with other profiles or logons, add the "Modify" permission to the "Users Group" on the app installed program files folder.

 

If P3D is installed into the default Program Files folder, add the Modify permission for the Users group on that folder so that addons that expect write permission there can write to their files without special privileges.

 

Problems from unnecessary path length mentioned in the guide do not manifest from the storage system itself which uses virtual FATs and addresses are all the same. Instead long paths can present a problem with certain apps when they convert relative paths into real paths. In general it's not an issue.

Yea, I have a question... where is this "guide" everyone is raving about? Is it pegged or linked somewhere?

 

Nevermind... found the link from another site, ha!

Yea, I have a question... where is this "guide" everyone is raving about? Is it pegged or linked somewhere?

 

Nevermind... found the link from another site, ha!

 

From another "site"..?

Inclusion of Arno Gerretsons Autogen Configuration Merger utility