Andydigital

Do you have the service packs installed for FSX? The log would suggest that you are using the original release from 2006 if I am reading it correctly. If you don't have SP1 and SP2 installed then that is likely where the problem lies.

The log file above says you are using version 4.57 which is not the latest version.

Its messed up because there is no announcements section anymore, it can probably be fixed by a moderator or admin by changing the post type. To be honest though this forum section of Pete's could do with a bit of house keeping, it needs a couple of new sub forums creating in it, maybe one called FAQ and another for things like LUA scripts and other pinned user created topics, that would certainly clean things up in here. You can also go into the user settings for the board and change the amount of topics that are visible of a single page, if you leave it set the way it comes by default you have to go to page two before you get past all the pinned topics, if you set it the the maximum of 40 then things aren't so bad. I actually prefer this forum software its so much better than PHPBB, its just a shame that this software is so expensive otherwise I would be using it myself on the forums that I run.

Just try it on the PC you have problems with first.

Like I said up until a few days ago when I started using beta version 625 of ASE the sky never flashed, so I've no idea what has changed, the only other thing I've changed in the same time period is my graphics drivers for my nvidia 285 GTX so it's possible that they could be the cause too.

It sounds like the window is out of bounds so to speak i.e. its become lost off the edge of one of the screens. Try disabling the second display temporarily and just use the one display and see if the log window comes back again the next time you start the sim and use the logging facilities.

You need to update wideclient first before Pete can help you further, please see the post below for download details. Updates and other goodies

It never did it for me until the recent beta version of ASE, I'd have a word with Hifi first.

For starters you need to use a supported version of FSUIPC, 4.57 is getting quite old now and is not supported anymore, you need to be using a minimum of 4.60. Details of download locations are in the thread below. http://forums.simflight.com/viewtopic.php?f=54&t=81475 If you still get the same error after installing the latest version just click on "Yes" and FSX should load normally, its an erroneous bug in FSX and there is actually nothing wrong with the dll at all.

Sounds like your problem is caused by Mcafee if FSX and FSUIPC works properly when its disabled, you should be contacting Mcafee about this problem not Pete. You will probably find that there is some way of creating an exception in Mcafee so that it ignores FSX and any programs that try to connect to it, again you will need to contact their support if you don't know how to do this.

Using the same email address is no longer required, just make sure you have the latest version of FSUIPC installed and it should accept the different email address when you enter the information into the installer. Details of download location can be found in the post below. viewtopic.php?f=54&t=81475

Thanks Guenter the TCAS mode selector is working fine now, I've also assigned a few of your other new commands too and they are also working great. Cheers.

Send a big hug to Paul Midd from me and a couple of thousand other Airbus X fans as well then, those fast increase decrease parameters are the icing on the cake. :wink: Did you find the TCAS mode selector parameters yet by any chance on your travels? Do not go hunting for them now if you haven't found them yet, it's no big deal just a gentle reminder from our email last week, you deserve a break from this anyway, time for you to go flying this wonderful bird for a while and enjoy all the wonderful work you have done mate. :lol:

Hi Guenter/Pete, Yes the updated Lua for the Airbus X throttles is working brilliantly, thank you to both of you.

If the ATHR is off then the throttles work like a Boeing, also bringing the throttles to idle disengages the ATHR if it was already on, moving the levers to TOGA detent enables the ATHR or a least it does in the AS Airbus, I'm not sure if this last part is realistic or not from some of the comments I've read on the forum. It's a beautiful little plane though, the VC is truly stunning, its just a shame they didn't do 2d pop out gauges for the PFD and ND because they are a little bit too small to read the detail clearly, and not doing a 2d MCDU is unforgivable in my book even though its not very complex.

Install FSpassengers again now, you will probably find that it is working ok now. If its not uninstall FSUIPC and reinstall again and that should fix it.

First of all update to the latest version, you will probably find that this fixes your issue. http://forums.simflight.com/viewtopic.php?f=54&t=81475

You need to update FSUIPC first before Pete will offer you any support, please see the post below for details of how to update. http://forums.simflight.com/viewtopic.php?f=54&t=74352

Isn't this the third post you have answered for Ronald on this subject now, I presume he lost this post too :D

Welcome to the world of Windows Vista and Windows 7, the first couple of things all none novice users should do after installing these operating systems is turn off UAC and remember to not install any program that is older than 24 months into the default program files folder.

viewtopic.php?f=54&t=74352 :roll:

Make sure you actually run the simulator and have a play around in an aircraft for a few minutes before you close down and reboot ready for the next step, service pack, otherwise FSX wont have initialised properly after each install stage. EDIT: You beat me to it Pete :)

Yes of course it is, just make sure that the XP and Windows 7 machines are in the same Workgroup, Windows 7 uses a different name by default so you will have to change one or the other system to match.

I think you failed to notice the point of the thread, this is for non-compatible aircraft and NOT for ones that do work with macros. Adding both to the thread will only cause total confusion and someone may end up wasting money as you put it because they thought they read a particular aircraft in here was compatible. Please feel free to delete this post and any other superfluous posts to keep the thread easy to read.

What I meant was that I would have thought Mauro wouldn't mind testing the Lua for you once you have made him one to test, or is that not what you were getting at? Then I was just saying thanks for helping Mauro with his problem.