jimgem

Of course it's v.6.16. I just wanted to be sure that you guys were paying attention.

I recently upgraded to v. 1.16. Everything seemed to be working well, but during my last several flights the program would not issue a landing clearance. The program issues all the necessary approach vectors and instructs the first officer (operating radios) to contact the arrival airport tower. The tower is contacted indicating that the aircraft is on approach for the assigned runway. The tower responds to this communication, but no landing clearance (or any other communication) is issued after this point. I ran the indexer a couple of times but with no effect. The odd thing is that sometimes I get a landing clearance and sometimes I don't. Recently, I have not been getting a landing clearance. Has anyone else experience this issue? Did I forget to complete something in the setup? Any ideas?

Ron:Thanks for the information. I fiddled around with the administrator privliges and got RC to accept my registration key and to run OK. The other thing that I did in the advanced properties box was to have RC run in XP SP3 mode. I don't know if the latter is necessary, but the program works.Thanksa again,Jim

I recently upgraded my PC from XP to Windows 7 32 bit. I also upgraded to RCv4.3.3845. Upon receiving my new registration key I attempted to paste it into the registation box. Initially, upon startup using the exe with administrative privliges, I recieved error messages indicating that "Component mscomct2.ocx or one of its dependancies is not correctly registered: a file is missing or invalid. After checking the forum, I discovered how to register this module through the cmd prompt. In trying to start RC again clicking 'Run as Administrator' I no longer get an error message, but my License key is not accepted. RC starts, the registration box opens, I paste the key, but after a few moments the box disappeared and RC does not start up. If I restart, it again opens the registration box indicating that the version is unregistered. I can just double click on the exe to open RC but when I hit start, It Show the 'IPC Timed out all retry' error. Any suggestions? I'm running the program as an administrator and I even tried to disable Norton Antivirus, but no luck. This is probably some issue with WIN 7 security, but I'm out of ideas.Jimgem

I have been using the J41 since its release and it has been a great add-on, particularly with the addition of FS2Crew Voice command. Several days ago I tried to fly the J41 and it was not possible to use any of the pop-up windows (no click spots, no wheels). I tried re-installing but no dice. Since FSX started running very slow and not loading correctly, I thought that there may have been a problem with FSX. After doing a re-install of FSX the problem was not corrected - as a matter of fact it got worse. Since I was planning to upgrade from XP Pro 32 bit to Win 7 32 bit, I thought that this would be a good time to do it. I just installed the new OS and installed FSX and SP1. FSX seems to be running OK. I loaded the J41 from the DVD and got an OK on the validation - bit still no pop-up controls. When I click on the window, I only get a flash of the window borders.Any suggestions? I can't figure out if there is a missing program or what?System: Dell XPS Duo Core 2 E8500, 3.16GHz, ATI Radeon HD4870 1GB GPU, 4GB Ram

Bryan:Thanks for the advice. When calling for the pushback and engine start, I was omitting the word "the". In the future I'll be careful to use the exact phrases.Jim

Bryan;Recently purchased the Voice Command Edition for the LD 767 and have been having a great time with it. The only glitch that I have been experiencing is when I request push and start. Everything is fine up up to the point where I call "Cockpit to ground". The ground crew responds, but when I say " ready for pushback and engine start" I get nothing. If I push back manually, the FO will start engines when directed and the flight proceeds normally. Am I missing a trigger word or action? This glitch is occuring consistantly.Great product - keep up the good work.Jim

Bryan,The only other add-on that I run is Radar Contact. I have run FS2Crew both with and without RC and it doesn't seem to have any effect on the problem. Any clue as to why turning off a generator brings the lights, radio and GPS back on? If I turn of the #1 generator, it also turns off the autothrottle arm switch. When I turn the A/T arm back on, there go the light. Come to think of it, arming the A/T during taxi is what sometimes triggers the lights-out.Maybe its time to try a complete reload to see if there may have been a corrupted piece of code somewhere in the mix.Thank for your help.Jim

Bryan,PMDG is up to date. All light switches move but the lights will not turn on.I switched from FSUIPC 3.7.4 to 3.6.5 and the lights seemed to work at takeoff but would not turn on at landing. Another very strange thing, when the lights or radios cut out, I can get them to turn on again by cycling the Generator toggle switch. This fix would not last, however, if I put the generator back on line. Once the Gen was back on line the radios, lights, GPS(I did install the FS9 default GPS, but I also tried running FS2Crew without it and it didn't make any difference) would again cut out after several seconds. I have been having some difficulty in getting the FS2Crew CD to boot up. The autorun feature does not work well and I have to remove it from the CD drive and reinstall it several times before it boots. Could the CD be defective?I don't know if this helps or adds more confusion.Jim

BryanThe PMDG is current having been purchased within the past couple of months. No service updates are indicated for the Professional Edition on CD. As for FSUIPC, I installed the newest version (3.7.4) prior to installing FS2Crew. All keyboard assignments are default.I was wondering if there is anything in the new FSUIPC that could account for this problem. I have also noted that the lights going out are always preceeded by either the ground crew or the FO saying something. The last time I ran FS2Crew, the lights worked fine until the FO ran the below the line take off checklist. On another occasion, the lights were turned on but when out as soon as the ground crew reported "push complete, set brake. etc."Jim

I just recently installed FS2Crew Professional Edition on CD with the the PMDG 737TNG (without the 800-900 Upgrade). I loaded the program for the 600/700 model without the 800/900 upgrade.Everything seemed to be working OK until I attempted a night flight. After pushback, engine start, after start checklist and taxi checklist; I turned on the taxi lights and headed for the active. Prior to reaching the active the taxi lights just quit. The landing lights did not work either. When I loaded the same flight(using the default FS9 flight planner) but did not activate FS2Crew, the lights worked fine. Is this a known issue or is there something that needs to be tweaked in the setup? I also have been experincing some difficulty with nav radios also stopping abruptlyThanks for any help you can offer,Jim