Jahanzeb

Cheers. il look into it. thanks

Hi everyone. first of all, i looked through all the pages and topics, and couldnt find the answer to my problem. i apologize if this topic has been dealt with. so i finally started building my 737 cockpit, starting with the overhead panel. since i cant get my hands on any I/O cards like BU036X, i had to resort of joystick hacking. After taking a cheap joystick apart, i realized how hard it was to solder those minute connections on the board. took me 2 days to get about 10 switches on that thing. after a successful solder, i check the connection with a multimeter before sealing the solder with silicon using a silicon gun. upon connecting the controller to the pc, i had no problem. tested the joystick with connecting toggle switches, and it worked fine. so i pulled out the cable, and started connecting the rest of the switches, with ever-growing excitement. when i was done, i plugged in the joystick, and to my disappointment, it said, USB device unrecognized. no idea what happened. my best guess was that the hear from the iron destroyed the IC or micro controller. or maybe it was the hot silicon. in either case, i looked into online solutions and found USB keyboard hacking. did more research, and it sounded like a good idea. something that might work, I had two options. to go with an old keyboard, which does not have matrix, but individual keys. the other option was, more easily available, modern USB keyboard. so i decided to go with the latter. I quickly opened up the keyboard, to discover two transparent sheets of plastic, with copper wire running through them. as per hacking guide, i took upon the painful and arduous journey to resolve the matrix. A few days later, after i had all the keys, i connected two toggle switches to the PCB with the keys "A" and "B" respectively. opened up FSX, loaded PMDG 737, went to FSUIPC, keys, created a MACRO for the Taxi Lights and Logo Lights. programmed FSUIPC for no repeats and there i had it. both switches turning on and off together and independently as intended. excited, i starting the physical construction for the overhead panel. took me a few weeks to wire everything, finding and putting in switches, even mounting the overhead panel. wiring the darn thing turned out to be pretty complex. thankfully, i kept it organized from the beginning. Next came the programming of every single switch. creating MACROS all the way. upon testing the switches one by one, they all seemed to work as intended. but thats when i hit a rock. when i turn on 3 switches on the same circuit, the switches wont turn out. scratching my head, i opened word, and tried the same combination of switches with a keyboard and realized that the keys "KCD" cannot be pressed together. apparently i need a better keyboard for that. some "N" type keyboard. even that doesnt allow more than 12 keys to be pressed down at once. ive been researching this for a few days now. and have come back with a blank. here are a few solutions i can think of: 1. using relays and capacitors for momentary key presses. (im no engineer. so no idea how to read schematics or go about it) 2. maybe use an older keyboard? the ones that did not have matrix. i dont know how many key presses they allow. 3. go back to using a joystick/controller and be careful with the soldering. 4. maybe FSUIPC has a solution? the advance user guide is french to me. 5. off the shelf I/O cards. something that is not delivered in my country. so kinda pointless. 6 maybe a keyboard emulator software that allows momentary key press Any help would be appreciated. ive spent a zillion hours on this thing. i dont want to give up. Especially when i'm so close. Joystick hack Work in progress

Hi, I've started building the 737-900 NG overhead panel. i printed out the exact overhead panel picture, scaled it to the actual overhead panel size, attached all the switches. stripped a keyboard. found the matrix combination. used FSUIPC to interface with the PMDG 737 OP. its alot of work (and fun) and i should be done with it in a few weeks. so I wanted to ask you how you're building the MCP and EFIS sections. Oh and the FMC. I was thinking of using the keys of the old keyboard for FMC keys. but they are kinda big. It would make a larger than required FMC . How do you use MCP switches? like altitude or speed? im sure you need a pot for that no? if so, how can that be used from a stripped keyboard. P.S i dont know how to use offsets in FSUIPC. i just create macros and assign a single keyboard key

update. its not because of corrupt coding in the downloaded SIDS/STARS. tested at other airports. it always happens when i select a SID or STAR, choose a runway, and then instead of hitting execute, i hit legs, and click on STEP, to see where the route is taking me. when i go back to the DEP/ARR page after pressing erase, i get the program pin error. so logically the next test should be, that i hit execute after selecting a SID or STAR, check the LEGS, if unsatisfied, change the SID/STAR. will update

I've gotten a program pin error several times.so here's what i did to get the problem in the first place. i was at VNKT (Khatmandu, Nepal) planning my flight. Unfortunately I didnt have charts for that airport, so i couldnt decide which SID to select. So i selected a SID on the active runway 20, and set the ND to plan mode. after every SID i presses LEGS on the FMC to see where the SID was taking me. (unprofessional I know, just couldnt find a chart) If the SID wasnt right, without activating it, i went back to DEP/ARR page, and selected another SID. After 5 or 6 times of repeating the process, the FMC said, "program pin error". I pressed CLR to get rid of the error msg, The FMC displayed the SIDS and runways, but when i selected them, nothing happened.When i restarted FSX, everything was fine, and i was able to take off from a selected SID.same thing happened at another airport. so here's something in common between the 2 airports. i downloads SIDS/STARS from simroutes.com for these two. Maybe the sid/star was buggy. just a thought.

hey simmers. ive been flying the MD11 for years, but since recently, i have a strange problem with my taxi lights and landing lights. when i turn them on, they dont fall right ahead of the aircraft, but way further on, on the taxiway/runway. I've started having this problem ever since i installed REX. I know that if i probably reinstall the aircraft, the problem would be fixed. but I just wanted to know if there's another way to deal with this, for example changing some values in the aircraft.cfg file? i have alot of liveries installed, so i dont want to uninstall all of them and then reinstall them. help anyone?

absolutely mind blowing textures and VC. cant wait for the in flight video and start up sounds. which type of engines will the ngx have?

hi everyone. im considering upgrading my desktop pc, since currently im runnnig flight sim on my mac book pro through hdmi to my 24 inch LED at 1920 by 1080.i have a choice between 5770, 550ti and 460 since i want to upgrade the cpu to atleast an i5. furthermore, i'l be running the following addons in fsxtraffic xREXPMDGand i might buy a few airport addons.in my experience, traffic x realllyyyy slows down my laptop. im able to get 20 fps if i turn down eveything except global resolution and aircraft cockpit.so basically i want to know which i5 would be the best for me, since im not going for a very high end machine, and which card would be the best. im thinking gtx 460 gives the most bang for the buck. im really confused abt the cpu, since that really boosts up fps in fsx since its cpu intensive.. but wil a 460 be an overkill? or can i get eveything to high on a 550ti with an i5

hi everyone. I finally decided to take that bold step, and build an overhead panel for my LDS 767-300. first step was to get the switches to work. the best way to do that is by purchasing BU0836X. unfortunately, they wont deliver the product to my country, so im forced to look for alternatives. I stripped down a joystick, and soldered two wired across the board with a toggle switch. tested it, and it seemed to work in windows.next i started FSX and FSUIPC. in the buttons tab, i set the toggle switch to landing lights on, when the switch is pressed, and off, when the switch is released. to my surprise, it was working fine with all FSX default aircrafts. but as soon as i switched to LDS 767, it didnt work.. didnt work with PMDG 747 or MD 11. works with all other planes, including wilco planes. next, i decided to set key assignments, from the level D tab in the alt menu. for some reason, it didnt read my joystick button at all. with FSUIPC, the button is recognized immediately.not trying to give up hope, i googled my problem. i came across a software called FSCONV. I read the entire manual that came with the software, which basically said that, that software creates offsets and connects to FSUIPC once FSX is loaded. i still didnt manage to control the taxi light with the button. i dont really know what offsets are, but i think i need offsets for complex aircrafts like the ones stated.project magenta offers a few offsets, but i dont know if they can be used for general purposes.I need help. ANY advice would do. I dont want to give up.

lol i feel stupid.. Thank you. got it :)

hi kyle.. im sorry i was unable to create my real name in the last post.. but ive looked evert where in my profile settings. i couldnt find it. so instead, i changed my display name to my name. is that good? im sorry, im new on this forum dude you are a hero! got the lights to work! thank you very much.. i dudnt know REX2 was out.. i have REX installed.. restored it to an earlier date, deleted my theme, unchecked the landing lights option, n viola, the lights are perfect now.. mercie

hi everyone. i've been flying the pmdg md 11 for a year now, and by far its my favourite plane. but since yesterday, ive started having this weird problem. when i turn on the taxi lights, the light shines very far from the plane, and a lil towards the right.. same goes for the landing lights.. i did not alter my aircfaft.cfg file, as i would guess, would contain information about this issue.. i havent tried reinstalling the plane yet. wanted to know if there's a fix.the only thing that ive done different is, shift from dx9 to dx10 then back to dx 9. it was working fine in the first two instances. the only new thing i've installed, is the wilco 777, which sholdnt cause a problem right? any help would be appreciated. its not a big issue.. but it a bit annoying

to be honest, i thought the model was pathetic. im always on the look out for a 777 for fsx. havent tried the pss.. but everything abt it was horrible. except for the exterior model. no IRS, no 3d knobs in VC. the fmc is really crappy and unrealisitc. obviously its better than any freeware out there, and all the stock planes in fsx, but i was REALLY disappointed.. i had read a few good reviews abt it. it was a waste of money. i dont think il be investing in wilco again. didnt like the sounds either. replaces them with TSS 767. i was annoyed that i couldnt touch half the buttons in VC mode even autobrakes, and alot of things were missing. but mainly why im giving such a horrible review is probably the fmc. for most ppl it doesnt matter.. for me, a good fmc counts alot. the pmdg md 11 has the BEST fmc thats out there.. followed by pmdg 747 and flight one 767. the only planes i like.. but hey, its just my two cents. ppl love the aerosoft airbus x which doesnt have an fmc at all.. all depends how u fly. if u just wanna sit there, and control the autopilot, then its not a bad plane at all..my question.. how does the pss match against pmdg? or flight one planes? worth buying? or just wait a year for the pmdg 777? (for which id gladly pay 500 dollars of i had to) (no i dont work for pmdg :( )

problem solved by deleting missionpanel.cfg

i know that im like a year late, but i was having the same problem.. the g2d error caused by FSP and MD11.. here's what i did.. i opened the panel.cfg of the MD11, and deleted some windows of the cockpit that i dont use (since i use VC) and the window error was no more.. but for some reason that was only restricted to Fsx Sp1.. when i installed sp2, i've started having the same g2d prob.. i've read alot abt it, and deleting the mission some cfg file is the suggested solution.. will try that out.. but just to let you know, u can always access the panel.cfg file in sim objects\airplanes\MD11 folder.. but do so at your own risk, and make a backup before u change the cfg file.. cheers

ok after running alot of tests, and gpu driver updates, i've concluded that the g2d error is caused by Fspassengers.. Fspassengers works with EVERY planein fsx including payware, except the pmdg md 11.. another conclusion, in fsx sp1, i managed to fix the problem, by editing the number of windows in the md 11 panel file as fspassengers does not allow more than 64 windows..anyway doing this did not work for me in fsx sp2.. il keep looking i guess, unless someone else is going through the same thing

thanks for all your help man.. but i ran into a strange problem without really doing anything. when i click on any panel in VC, it doesnt pop out like it use to.. n this goes for ALL the planes.. even stock fsx planes. furthermore, i cant use see the cocpit at all.. only virtual cockpit. left me scratchin my head. tried everything, i figured it had something to do with some window being disabled. the last thing i did was play fsx online and was tower control.. now that im writing this, i remember fading out a window there.. but was unable to bring it back.. anyway, il have to install a fresh copy of fsx :( and all the addons Actually that makes alot of sense.. i download new video drivers recently, and when im even watching movies, they seem to stop working for 2 seconds, and the screen goes blank.. and it says, windows video drivers stopped working but have recovered. Thanks alot man.. il revert back to the orginal drivers, or wait for further updates

Test number 1uninstalling software "trafficX"running fsx in dx10optimizing graphicsflight without FspassengersResult:the flight was a complete success.. flew LTBA - LIRF (istunbul to Rome) without any crashes on the PMDG MD11 (phew). one of these must be the culprit then.. If anyone is having similar problems, try doing the same thing

thanks alot man.. looking into it

hi everyonei dont know if this topic has been covered before, but i couldnt find it.. anyway, i have fsx sp2 and whenver i take off, fsx crashes randomly.. sometimes during taxi, sometimes at the terminal, sometimes, half an hour into the flight. i havent tried removing all the planes because its so tedious reinstalling all of them back again. i have the following addon planes:flight one Atr 72-500aerosoft airbus xan225 (feeware)carendo c240, 208, 172, 152flight one md super 80 serieslevel d 767wilco a 380pmdg 747pmdg md 11and one random atr 42 freewarethe reason for listing the planes is, there could be a conflict somewhere between the planes? i dont know. when i googled the error, it said it has something to do with texture error caused by addons.. when that faulty texture is generated in fsx, it causes it to crash. and it mostly related to scenery addons.. (which i dont have any)anyway, so i uninstalled sp2 and guess what? the plane flew like a charm.. no more crashes. i flew long flights without and hiccups.. so was that the solution? probably. but a new one arose. i need sp2 to fly my level d 767.. and personally ive read that sp2 is more stable.. anyone has any opinions? anything? i just want to fly my md 11 in fsx sp2. THE greatest plane thats out there!!im running windows 7 64 bitthrough apple macbook pro (yeah yeah.. dont comment on that)4gb ramnvidia 320m graphic cardhdmi out, 1920x1080 resolution(dont think any of this should be the problem though)other hardware- saitek yoke and TQoh and i always use Fspassengers.. hmm maybe that could be it.. but it runs fine with every plane out there.. and with md 11 in sp1any help would be greatly apprecaited