AlexCheng

Hi guys, I use the FSCopilot GPWS addon for planes that I don't have the callouts on. But is there a way to change the GPWS callouts provided by FSCopilot? I want to use the 777 style callouts instead of the 737, 747-ish callouts provided by FScopilot? I tried replacing the files with the new ones but there will just be no callouts. Is there a method of doing so? Plz help.Alex

NP, I've got the plane up and running thanks to some help from the others. It works great now. Thank you sir.Alex

Can you PM me your AP_control_coeffs.dat then? xD (It says that it was last modified in 10/23/2005, dno if it is the original or not)I'm a bit lazy to reinstall. =DAlex

Yup sir, I have edited the 773ER aircraft config with your settings, and replaced the .air file with yours.My POSKY 773ER actually comes from the "Mega Merge 777" months ago i found from someone else on the net. But i just took their exterior model and panel.cfg, it shouldn't have much of an effect right? Your FDE tweak only affects the aircraft.cfg and the .air file. But as I said again, the plane is flying like mad with your settings. Any help would be appreciated.Alex

sorry to report but it seems like the B773ER config has some serious problems. =(On my first try, after it takeoff the plane was climbing but met turbulence. The plane immediately transformed into a dolphin after hitting turbulence. (going up and down, up and down...... non-stop, although it was still climbing)On my second try, the plane took off but failed to engage VNAV, at around 18,000 feet i disengaged the autopilot to see if i could fix the problem. Immediately the plane rotated to 90 degrees and stalled. I got out of the stall, but the plane decided to make wild maneuvers all over the place, and I finally crashed after fighting the plane for a min.Please help, is there any solution?Alex(P.S. your .air file for the B773ER actually works well on the default PSS 777 though! But not with the merge, im sorry)

Wow now it works. Thx for the help guy.Alex

Hello,My PSS A340 systems are working great. However, when I switch to VC mode, there is a problem with the views. The A340 cockpit chair is blocking the way and I can't see the displays. It seems like the VC seat has been pushed back. How can I modify the panel.cfg or fix this situation so I can see the VC normally? I have tried reinstalling but to no avail. Note: The A330 works fine. Just not the A340.Thanks,Alex

hello,for the past few days I have been trying to repair simconnect. But now it even says that ASX cannot find the *simconnect.dll. (despite the fact that it is actually there) I have no idea on what to do now, I have reinstalled FSX like 3 times already and installed those SDK updates and tried to get that simconnect.dll to be found by ASX, but to no avail. Is there any solution out there? Thanks,Alex

Ok, for the AI Traffic, I finally understand what you actually meant. After I run the AI Traffic application, it just automatically quits. Anything else to check? Thanks,Alex

Hi Jim,Thanks for the reply. I use norton 360 for my computer's security. On the norton firewall (windows firewall is not turned on), I have already allowed the Xengine, Xgauge, FSX to do anything it wants. But when i try FSX again, there is no difference.As for the AI Traffic, I don't use any AI since I fly in vatsim mostly. Do you have any more suggestions?? =[Thanks,Alex

Hi,I have been desperately trying to fix my ASX for the past couple of days. It seems that ever since I updated to SP4, ASX simply does not work anymore. I start FSX and then start flight, it says "ASX connected!" and "initial weather depliction complete" (or something similar to that). But, no weather has really changed from the default settings (fair weather), meaning 15 degrees, 20 miles visibility, clear blue skies.. etc. I have read other posts regarding sharing and errors on the log file. I am sure that there is no error within the log files, there is no "error recieved" line on the log. As for sharing, I have shared my FSX program folder, and FSX files folder already. Also, I am an admin on my computer and have checked every option on the permission rights for all users on my computer when I use ASX. (ones when you right click on the shortcut, and security tab).Please give me some suggestion on how to fix this problem. ASX used to work for me!Thanks,Alex

Hi guys, Im new to this forum. Recently i went to my friend's house, he had the PMDG 747X setup, FSX, and FS2Crew. He was also having the TOGA button problem. I've noticed something that might be able to help you guys. (I am not sure).In the flight planning page of FS2Crew, theres the T/O performance section. Then there's the T/O power part. Now I've noticed that value to stay at somewhere between 90-120? I am not sure sorry. If we reflect that on the PMDG 747, the thrust setting should be the same as indicated above the engine indicators (in decimals like 1.xx). For the GE variants, I noticed that yes, the TO thrust settings is inputtable to the T/O power part of the flight planning page (eg 1.02 thrust on PMDG, set to 102.0 on FS2crew). However, for the RR and PW engines I have noticed that the takeoff settings are way above. It is at like 1.67 or something. If I do the same and put these values into FS2crew, (should be 167.0... maybe), then the values would be correct right? However, in FS2Crew flight planning page, you cannot change the T/O Power part all the way up to 167.0. Maybe this is the reason why TOGA is not working for some of us? (in particular RR and PW engine 747s)?I am not 100% sure. Just giving a suggestions. Hope it helps. Cheers.Alex

Hi everyone,I went to my friend's house and had a look at his FSX, PMDG 747, and FS2Crew setup. He was having the TO/GA button problem also. I have noticed something very interesting, maybe it can help you guys also.In the flight planning page, there is the T/O performance section right? Then there is T/O Power. Now... the value is usually 1.0... something right? Now if you use the GE engines, the takeoff values are 1.0... something also. However, when we look at the RR and PW engine variants, their T/O power is at 1.6... something? I dont think that you can adjust the T/O Power on the flight planning section all the way up to 1.6 something. It stays at 1.0 something to 1.1... something. Am I correct? Maybe this is the whole problem to the TOGA button not working?I am not 100% sure, just a guess. Hope it helps. Cheers.Alex