At the risk of sounding condescending, as I have no idea of your level of familiarity with Windows Explorer... Among the Windows standard option when you right-click on a file should be "Open with..." Hover your mouse cursor over that selection. The menu should expand and include "Choose default program..." at the bottom. Click "Choose default program..." which will open the "Open with" dialog box. "gMotor 2 MAS File Utility" should be in the "Recommended Programs" list at the top. If it is, tick the check box below the list frame "Always use the selected program to open this kind of file" meaning of course, files with the .mas file extension. Then click on the "gMotor 2 MAS File Utility" icon and then the OK button. This should reestablish the default program for opening .mas files. However, if it is NOT in the lists, either "Recommended programs" or Other programs", then click the "Browse..." button and navigate to the "MAS2.exe" file located in the C:\Users\[yourname]\My Documents\rFactor2\Support\Tools\, double-click it or select it and click "Open". Again this will reestablish the default program for opening .mas files. If this get's you to the point where you can open the MAS in the MAS File Utility, you may wish to avoid extracting directly to the TrackMap Tracks folder. If you have User Account Control (UAC) enabled in Windows, it may may give you some fits and refuse to extract directly to that folder. Extract them to your desktop instead and then drag'n'drop them into your Tracks folder at which point you should get the administrator permissions dialogues in order to complete the process. If you double click on an MAS and you get a pop-up stating "Unknown MAS key", you are trying to open an encrypted archive file (e.g. 32_PIXEL's Lester track). Forget it. You will have to use the method described in the TrackMap documentation (C:\Program Files (x86)\rFactor2\Plugins\TrackMap\Docs\TrackMapv0_91_ENG_Faz.pdf) to create the required files manually or see post #190 of the "Celica gto IMSA + semi-fictional track" thread.
All the objects are flickering on the new Mountain Peak track, anyone else finding this or know how can i stop it doing this?
Any update planned since last rF2 update and new UI displays track incorrectly and in bad screen positioning when in racing lobby?
No need, you can adjust these settings with TrackMap ini... //Edit: it would be a lot of more important, to fix the wetness on track feature now... ;-) Build 930
Can you help me how to do that? And yes, i agree with you on that, also new tire model changes won't affect display wear calculations?
Have a look into trackmapconf.txt. There is a section "[MAPINBOX]", where you can change the position of this map. In E:\rFactor2\Plugins\TrackMap\Docs you can find a documentation (pdf).
is anyone getting lap timing issues if they escape to pits?...testing last night the trackmap timing would keep counting if you didn't finish a lap and add it on to your next completed lap
After few investigation, here some advice for using the 0.96 with the build 930. First of all now on rFactor 2 (as written into the release note) takes care of the "amount" of rain on the track, mainly on the main fast path. Due to the real road feature, rF2 can show parts of the track with less amount of water (rain) and other parts with more. Into any TrackMap "meteo" widget where are already present the "Wetness IN" and "Wetness OUT" values (like the MeteoRFE widget), you will find the "Minimum" and "Maximum" rain depth! We have only to change the text but anybody can do it editing the tga file... What is important to understand is "how the numbers work": 50 indicates that the track is fully "damp", but there is NO standing water! FROM 50 TO 100 is increasing the amount of standing water up to a nominal maximum. Internal values of rFator2 are fractions of unit: 0 to 0.5 and 0.5 to 1.0 Another important point is the new section added into the HDV file that manages "sensors" for plugins... typical example is the HDV file in the last version of the Skip Barber: [PLUGIN] // Whether certain sensors are available as telemetry outputs AerodynamicSensor=0 // Aerodynamic force sensors EngineSensor=1 SuspensionSensor=1 TireForceSensor=0 TireTemperatureSensor=1 Pay attention: 1 means the function has been deactivated, 0 (zero) means the function has been activated and this last value at the moment interferes with some widgets like the WGL.
