bowingic

Thanks Mike...yes its one of the default airport ground vehicles...more than enough of them at KLGA. I also had them removed until Laminar fixed the synch of them across networked clients (my setup is similar to yours except a 767).

Hi Mike I've always appreciated your work on night lighting over the years. I have tweaked your lighting a little to suit my own tv's etc. One thing that bothers me at the moment (more a minor irritation) is the lighting on some ground vehicles. For example, in particular is the light behind the driver of the belt loaders...the spill is incredibly over bright on the back of the driver. This stands out and dominates particularly at airports where there is a lot of ground vehicle traffic and lines of vehicles are present (eg KLGA). It seems very unrealistic to me. I'm wondering if you have noticed that and if you might know how to tone that down. I have tried lowering the spill in possible places in the lights.txt but to no avail. I'm thinking it is probably built in to the vehicles rather than something in the lights.txt. I would be interested to hear your thoughts. Or....maybe I'm just being too picky, LOL!

I wonder if someone could point me to a downlink to a stand alone version of Sweetfx that is known to work on FS9. I have only been able to find the later Sweetfx associated with Reshade, and haven't managed any success with it. Perhaps because of the Reshade d3d9.dll mentioned above? Thanks for any help Ian

Simply Great James! Enjoy all your posts! Just wondering what your preferred or usual altitude is for these shots?

Thanks Sascha Slightly off subject, I wanted to try Sweet FX with EVO and used Rshade 2.0.3 with Sweet FX 2.0, but FS9 would stop during its boot. I had placed the D3D9.dll in the FS9 folder (along with the other Sweet FX files as per the instructions). Can you tell me which version of Sweet FX you are using and also which dll to use in FS9.? Also the instructions say to replace the dll that resides in the same folder as the exe (in this case the main FS9 folder) but I couldn't work out which to replace if there is one? Thanks for any assistance

Hi Sascha Just checking if your latest EVO 2015 update available for download yet? I checked Updates on Dropbox but couldn't find it. Thanks again for your efforts Much appreciated!

Google Never10....recommended by PC Authority Magazine (Australia)....safe and easy...and you can revert if you ever want to re-enable the messages. Ian

Not necessarily your mistake about it being FL90...some transition levels are below 9000 feet...in which case FL90 is correct....so you should have descended to 9000 feet but with standard pressure set as stated above ( rather than the QNH which you set). The pressure difference between standard and QNH was why you didn't reach the required altitude. Transition levels are usually shown on STAR charts.

Hi Jose I too am having a dissillusioning experience with Xaviation's licencing and support ticket policy. There is a program called Weather XP which has cloud textures...not sure how it compares with SMP which I really like, but can't use on my cockpit setup at the moment due the licence issue. I fear I too will have to cut my losses with SMP unless I get some further response (I have complied with all their requests). Cheers Ian

Hi Sam I was expecting the unexpanded size but not the windows opening on the same monitor. It is indeed odd the way FSX handles these scenery windows. I only ever had the one extra scenery screen when running from one pc so didn't encounter that issue. I suspect that FSX opens these windows in the same way it does when you open extra scenery windows with the bracket key (ie like a stack of cards) regardless of the flight file settings except for the starting position of Window 2 (at 1920 in your case). You might recheck you had 3840 for Window 3 in the FLT file...can you post the modified FLT file for me to look at. Regarding different aircraft, basically you need a to have a flight file for each one. The easiest way for you would be load up just your main front view for each aircraft texture without side views (except the one you have already setup of course) and save each flight with for example Carenado 172 Texture1 (or whatever the texture is called), Carenado 172 Texture2 etc. Then just copy and paste the Window 2 and 3 settings and their associated Camera settings (the one that has your zooms and rotation settings) from the FLT file you have set up with side views, to each of the other flight files. Then just send the FSSAVE file for each texture to the desktop, so you can launch each flt (texture) directly from an icon. I am interested to investigate the window positioning further, but I fear we may be up against an FSX idiosyncrasy in the way it handles loading of these scenery windows...no harm in trying anyway! Cheers Ian

Hi Sam Yes I would have thought (as you said) if you are able to move the side views to other monitors that they are undocked. Has the flight been saved with the windows in their side positions? That usually retains their positions if they are undocked, but not their size after reload. Try that and then check what the FLT file says for undocked cords. I should have told you to do it that way first...I'm so accustomed to setting things up in the file itself I forgot the most simple way. I actually told you a bad in regard to the comment I made about if the monitor to the left of the main screen in Windows Res Settings..then of course it would be the zero pixel position (not -1920) and the main FS screen would be at 1920. From your setup the Undoc Coords should end up as follows: Window 1 remains as is in your FLT file (docked) Window 2 1920, 0, 1920, 1080 Undocked Window 3 3840, 0, 1920, 1080 Undocked See how that goes Cheers Ian

Hi Sam Looking at your FLT file you could edit it such that Windows 2 and 3 are undocked (Undocked=true) and then set the UndocCoords to the appropriate monitor position. Also set Maximise=true for these monitors. For example if your first side screen monitor is immediately right of the main screen monitor (in Windows screen resolution settings) then you would have UndocCoords=1920, 0, 1920, 1080 If the third monitor was to the right of the previous one the it would have UndocCoords=3840,0,1920,1080 These settings will position your side views to their appropriate screens, so all you would have to do on start up is stretch them back to full screen size (as unfortunately although the position will be retained on reload the size will not, as I previously discussed. By the way if your left side screen is to the left of the main screen in the Windows resolution settings then you would have UndocCoords= -1920, 0, 1920, 1080 These edits should at least save you having to move the windows to the side monitors, even if you have to resize them. Cheers Ian

Thanks Sam I use the same method of hiding the 3 scenery window borders on my 767 simulator using 3 projectors, and running FS9...one pc runs 7 displays on that sim (good old FS9 :wink:) and still averages 30FPS. On the FSX GA sim I initially ran two of its three LED screens using one pc. I was able to set up the second (undocked) window to load on the second screen connected to that pc by configuring the FLT file but It would never retain its size on reload regardless of the FLT file configuration. I just had to grab it on the corner and stretch it out to fill the screen each time. I did quite a bit of research on trying to retain the window size on the extra scenery window on reload but couldn't find anyone who had achieved that with FSX. Panel windows weren't so bad as closing and reopening them bought them back to size, and there is also a panel save and restore freeware program that does that quite well. I use push buttons and Autohotkey to resize the panel windows after loading (it just closes and reopens the windows). P3D doesn't have that window resize issue, at least with its panels it doesn't...don't think I ever tried the extra scenery window. Of course I don't have that problem now with each scenery screen being on its own pc (expensive fix! LOL) I enjoyed seeing your sim. I imagine it would be quite immersive with no outside distraction. On my GA sim I positioned the window posts to hide the screen bezels. This make a big difference to the immersion and feeling of motion, as no doubt your setup would give. I like the way you can look out under the Cessna wing on yours! Thanks for sharing your info Ian

Hi Your setup is quite interesting. Thanks for your settings info. I also run a 3 monitor setup in a generic GA sim, but with 4 pc's. I assume you have 3 windows open but I didn't notice any window borders in your photos. I would be interested to see your FLT file if you could post it...I assume you start up with a flight configured for your 3 views? Cheers Ian

Have forwarded the PanelBuilderSender.cfg to your support email. Computer Language is Australia-English Yes I did specify "Add Instruments to Windows Firewall" during the install Thanks Again Ian

Yes Xplane 10 interface is version 2.94 as is the EFIS Addon...have tried uninstalling and reinstalling both but still the same issue? Thanks Ian

Unfortunately no...still the same problem. Have double checked all the C++ requirements etc, uninstalled and reinstalled the EFIS Addon and Xplane x64 interface. The other EFIS gauges I've tried all work I've run out of ideas as to what might be the problem with the NavDisplay on my system. Appreciate any suggestions. Thanks Ian

OK I found the EFIS Add-on Update to 2.94 today...sorry, I was looking in the wrong place. Expect that will fix the problem. Thanks Ian

Yes the buttons work...ie waypoints, vor's can be turned on and off, and the range toggled, but the map stays the same wherever I am, the aircraft symbol stays on the airport (KMSP), and the G/S, TRK and TAS displays stay on 000 regardless of what the aircraft is doing or where it is. Sorry, I should have said the map looks to be the same airport/map as shown in the EFISNavDisplay.jpg in the Instrument_EFIS folder rather than it actually being the jpg. Panel Builder Version is 2.94, EFIS Addon Version 2.8...can't see any later updates for the latter in the Update section on the website? Checked correct C++ versions present (installed during the Panel Builder install). Thanks Ian

I'm a newbie to Panel Builder. Have installed Panel Builder (Analog) and the EFIS Addon for Xplane. All the gauges I've used so far, work fine including the EFIS ones, except for the Nav Display...it just shows the jpg ( ie no map updating) but the gauge buttons (VOR etc) work. I'm using Win7 64bit fully updated and Xplane 10.35. I checked the Panel Builder folder and the exe for the gauge is there, and the cfg file in the plugin section of Xplane has the correct port with GPS parameters etc present. Is there anything I am missing? Thanks for any help Ian

After my full install using the 10.6GB setup. V2.3 runs fine. Went to install FSUIPC and found there was no modules folder? I created one but no Addons tab created in the P3d menu. Anyone else had this problem? Any help appreciated Sorry...my bad...needed to do a full install FSUIPC to create modules folder.

For curved screens you need a warping program like: http://www.fly.elise-ng.net/index.php/immersivedisplaylite2

Use EaseUS copy software...the basic version is free, works perfectly and has a simple user interface. No tweaking to the image. Just plug the imaged drive in and it works exactly as per the original. EaseUS creates a bootable CD from which the user interface loads and you select the source and destination drives. If its just imaging or partition copying I can't understand why people bother with Acronis... which isn't cheap. I guarantee you EaseUS will create a perfect image...try it and see (just Google it)