User Tools

Site Tools


simulator:log

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
simulator:log [2017/01/23 19:48] – [Troubleshooting - tm.log] jhsimulator:log [2020/05/10 22:13] – [Support] jh
Line 1: Line 1:
 ====== Troubleshooting - tm.log ====== ====== Troubleshooting - tm.log ======
  
-The most important resource for troubleshooting is the simulator's log file ''C:\Users\%USERNAME%\Documents\Aerofly FS 2\tm.log'' inside the [[path|user-folder]] of the Aerofly FS 2. +The most important resource for troubleshooting is the simulator's log file ''C:\Users\%USERNAME%\Documents\Aerofly FS 2\tm.log'' inside the [[path|user-folder]] of the Aerofly FS 2.
  
-This file logs all events during the Aerofly FS 2 Flight Simulator execution. It contains warnings and errors that might be generated when the new aircraft is loaded.+On Mac it should be located in ''Macintosh HD⁩/Users⁩/.../Library⁩/Containers⁩/com.aerofly.aerofly-fs-2-mac/⁨Data⁩/⁨Library/Application Support⁩/Aerofly FS 2'' 
 + 
 +This file is a [[text_files|text file]] that logs all events during the Aerofly FS 2 Flight Simulator execution. It contains warnings and errors that might be generated when the new aircraft is loaded.
  
 ===== Simulator Crashes ===== ===== Simulator Crashes =====
  
-When the Aerofly FS 2 Flight Simulator application crashes the IPACS support team (''mail (at) ipacs.de'') can help better when a copy of the ''tm.log'' is attached to an e-mail to them.+The ''tm.log'' file can be opened by any text-editor and will contain important information about the cause of the crash, usually towards the end of the file. Any "WARNING:" or "ERROR:" messages should be payed attention to. Often the issue can already be resolved by the user by looking at the tm.log file. 
 + 
 +When the Aerofly FS 2 Flight Simulator application crashes the IPACS support team  
 +(''mail (at) ipacs.de'') can help better when a copy of the ''tm.log'' is attached to an e-mail to them. 
 + 
 +===== Simulator Not Starting ===== 
 + 
 +Delete the main.mcf file to restore default settings. Then try starting the simulator again. 
 +Please see the [[simulator:mcf|Main Configuration File]] wiki page. 
 + 
 +Make sure your **graphics card drivers** are up to date. You can find the latest graphics card drivers on the webpages of your graphics card manufacturer. The automatic driver search of Windows may not return the latest drivers. 
 +   * [[https://www.nvidia.com/Download/index.aspx|NVIDIA Drivers]] 
 +   * [[https://www.amd.com/en/support|AMD Drivers]] 
 + 
 +Also make sure the correct graphics card is being used if you have multiple graphics cards or an Intel HD Graphics chip and a dedicated graphics card. Use the appropriate graphics card settings for this. 
 + 
 +We recommend to not create specific graphics card profiles for the use of Aerofly FS. Aerofly usually runs well with default settings and manually changing them could cause issues that we cannot replicate on our side. 
 +===== Support =====
  
-This log file will also note any issues with the hardware in use. +Please visit our [[https://www.aerofly.com/community/forum/|official IPACS Forum]] and use the search function to see if any other users are experiencing similar issues. The solution to most issues can be found there!
-===== Debugging =====+
  
-Common issues during own aircraft development are+And if the IPACS forum search doesn't seem to yield results you can contact our support team via:
  
-  * [[simulator:text_files|Syntax]] accidentally changed, pay particular attention to unmatched braces/brackets +   * [[https://www.aerofly.com/support/contact/|Contact Form]] on our official website or 
-  Spelling mistakes +   via mail (''mail (at) ipacs.de'').
-  * Same name used for more than one object +
-  * Object referred to does not exist +
-  * 3D objects used multiple times +
-  * Joint force and dampening constants to high +
-  * Output / Input not defined +
-  * Control message names not matched +
-  * Control message qualifier not set for a toggle switch +
-  * Infinite loops created by using the output of the same object or by chaining object to a loop without any object in the chain that can provide a delay (like a servoclassic or servolinear). +
-To debug a longer chain of connected objects one can simply overwrite the input property of an object by replacing the usual xyz.Output text with '1.0', '0.0or any other constant value. Note that inputs with an 'ID' in their name don't directly read the value but use a pointer object instead. It is possible to write a constant value into the InputID parameter of an object.+
  
-For debugging it is very useful to assign a key to the 'Reload aircraft' in the simulator control settings (available only if the 'developer' option is set to true in the 'main.mcf'). Using this function only the aircraft but no scenery is reloaded.+> Please include the tm.log file is possible and your system specifications, Aerofly FS version so that we can locate issues faster.
simulator/log.txt · Last modified: 2023/01/29 08:48 by jh