mawibo

Hi Patrice, I found and fixed the issue. The issue was not ILS specific, but affected almost all map symbol types. I did actually change something in the previous release that broke the proper generation of map symbols. Sorry about that. The new version is 5.8.6107.1518 and is available for download now. thanks again, Maarten

Hi Patrice, Although I haven't changed anything in this part of the application recently, I do notice the issue myself as well now. I am looking into it and will let you know as soon as I have a solution. thanks, Maarten

Hi Patrice, The latest version is 5.7.6106.36600. thanks, Maarten

Hi Edward, A new version is available for download now and the problem should be fixed. thanks, Maarten

Hi Edward, I found the issue and will release a new version this evening. For the time being, you can switch over to the dark theme. The dark theme does not have this issue. thanks, Maarten

Hi Edward, I will look at it and fix it this eventing. Thanks, Maarten

Hi Darek, Well spotted! Fortunately this .lua file is not yet used. Some GPS variables are missing in the SimConnect API and I will use this .lua file (together with the SLX_G1000.CAB gauge) to workaround this issue when I have made some more progress with the implementation of the G1000 PFD and MFD. thanks, Maarten

Hi Robin, Didn't you read the release notes? The auto start/stop settings for launch entries are profile specific now. You can find them in the profile settings. thanks, Maarten P.S.: the version number is constructed as follows: x.y.days since Jan. 1st 2000.seconds since midnight

Hi Ugo, I sent you a PM with a link to the latest version. thanks, Maarten

Hi Shahin, Please read the forum rule and sign your post next time. I already informed you via e-mail that I think I found and fixed the issue. thanks, Maarten

Hi Brandon, I did some tests, and it seems there's a bug in P3D that has nothing to do with SLX unfortunately (otherwise I would be able to fix it): when you save the graphics settings and the target frame rate is set to unlimited, P3D writes UPPER_FRAMERATE_LIMIT=61 into the saved graphics settings file and that's what you get if you load these graphics settings using a profile within SLX. To workaround the issue, you can set the target frame rate to 0 in the profile settings; this will properly set the target frame rate to unlimited within the sim. I also suggest you report this issue in the Prepar3D forum. I could do it myself, but you deserve the credits for finding this bug. Please also note that the graphics settings file (and of course also the prepar3d.cfg file) contains a PANEL_OPACITY setting. Opacity is the inverse of transparency: if opacity equals 0, transparency equals 100 and vice versa. thanks, Maarten

Hi Jim, Please send me a PM or an e-mail (e-mail address on the front page of the user guide) and I will send you a direct link to the latest version (5.7.6043.38743). Btw: you can post an image if you upload you image first to some server (e.g. fsfiles.org) and then insert a link to your uploaded image by using the image button on the toolbar. thanks, Maarten

Hi Brandon, What I do is the following: I apply to profile setting to the configuration file as specified in the profile I open the graphics settings file as specified in the profile I copy each and every setting found in the graphics settings file to the configuration file as specified in the profile I copy the configuration file as specified in the profile over the fsx(-se)/prepar3d.cfg file in the %appdata%\(Microsoft\FSX(-SE)|Lockheed Martin) folder In the next version I will change the order of the above to 2, 3, 1, 4. If you do not want to change the target frame rate, please set the 'Target frame rate' setting in the profile to -1. I suggest you do the following: exit the simulator save the %appdata%\Lockheed Martin\prepar3d.cfg file to a backup location within SLX select the Profiles window and then select 'Tools|Apply profile' on the ribbon compare the %appdata%\Locheed Martin\prepar3d.cfg file with the prepar3d.cfg file you saved in step 2 and compare these two files with the contents of the saved graphics settings file in your '[Documents]\Prepar3D v3 Files' folder let me know if you find anything that does not look right thanks, Maarten

Hi Brandon, Sorry for the late reply. I processed the graphics settings file, inserted the data in the config file, but forgot to save the config file. It will be fixed in the next version. thanks, Maarten

Hi Oliver, I saw in your log file that you have set SLX to close after launching the simulator. Does it make any difference when you uncheck this setting (Home|Settings|General|Close SimLauncherX after launch)? thanks, Maarten

Hi Oliver, Can you please send me your [Documents]\SimLauncherX\SimLauncherX.log file after you have launched the simulator using SLX? P.S.: you can always start the simulator manually (or by selecting Tools|Start Prepar3D on the Profiles window ribbon tab) and then use SLX to launch a flight thanks, Maarten

Hi Oliver, I think it is a Windows issue. I have seen it happen before, even with FSX and even without using SLX to start the simulator. When the main simulator window has disappeared, try to shift-right-click on the taskbar icon and select 'Maximize' or 'Restore'. I hope this helps. If not, please let me know. thanks, Maarten

;-) Maarten

Hi John, You cannot do that currently, but I will put it on my todo list. I'm working on a flight recorder/playback feature now: it's 90% finished; it works, but playback still stutters a bit. Thanks, Maarten

Hi John, Your flight plan probably has an error and most likely it's the cruising altitude. In some situations the validation of the cruising altitude is wrong (will be fixed in the next version). To workaround this mistake, you can select 'Ignore cruise altitude errors' on the Flight Plan ribbon tab. If this does not solve your issue, please let me know. thanks, Maarten

Hi Walter, As far as I understood, both issues (German characters in the message line and 'new aircraft detected') are solved now. Let me know if my assumption is not correct. thanks, Maarten

Hi Walter, I finally found the cause of the message line issue: it was a bug in the so called 'Beatles blog' managed SimConnect client. It converted every string back to UTF-8 before sending it to the simulator. I have fixed that now. As for the 'new aircraft found on startup' issue: please send me the complete log file and your %programdata%\Lockheed Martin\Prepar3D v3\simobjects.cfg file. thanks, Maarten

Hi Walter, The message on top of the simulator window still displays the original file name. I will convert that to code page 1252 in the next version. Hopefully that will make it more readable. thanks, Maarten

Hi Walter, I found the mistake and will release a new version later this evening. I changed the update mechanism, so hopefully it works as intended. thanks, Maarten

Hi Walter, Can you send me the complete log file? I need the stack trace. thanks, Maatten