matta757

Hi guys, I am having an issue with scenery at some of my addon airports and I cannot seem to figure out just what is going on. Here is a picture of the problem: This was taken during landing at Seattle (KSEA). As you can see, the area in front of the aircraft for some reason is letting textures other than the FlyTampa textures show through. I am assuming these are default textures. This area of show through contiues once I taxi off the runway and to the gate. It only seems to happen when flying TO Seattle, not when flying FROM Seattle. Additionally, this evening, I taxied way on the South end of the airport to my gate at the S terminal. This time, at some point during my taxi, the texture problem ceased and everything looked normal. I have tried removing the user addon to add the 3rd runway, this didn't seem to help. I have turned off my Manhattan scenery because I know it can conflict, but that didn't help either. This also happened at Manchester Intl, which is made by UK2000. Does anyone have any idea what could be causing this problem? Thanks for any advice. Matt

Question for you with this setup then... BRILLIANT idea, since MSFS does have progressive/taxi instructions. But the problem I ran into when trying your idea is that MSFS ATC wouldn't respond because everytime I hit a button (1,2,3, etc), RC interpreted that as an input. Is there a way to get RC to ignore your inputs when you're trying to speak to MSFS? I tried closing the RC window, but then when I pressed a button it would make the "beep beep" phone call noise and reopen the RC window, and there would be no response from MSFS.Any help would be appreciated!Thanks,MattP.S.- I think RC is terrific and I completely understand why this feature isn't available!

I have tried everything suggested by users here and still cannot get it to work. Jd, what do you mean by "insert missing file name here"? What exactly is the missing file name? Should I be entering the prompt into the CMD window EXACTLY how you have it written?It continues to tell me that it cannot find the .DLL file. I am running Win7 x64. This is becoming really frustrating, seeing as I just got this new machine, all I want to do is fly... :/Thanks,Matt

nope... just aismooth

Hi,I am having this same error. I have read through this topic and the other two you linked to and have not been able to solve it. I am NOT running WideFS, just the normal FSUIPC. Everyone else who seems to have this problem is on a Wide machine. I am not sure what to do and I am getting increasingly frustrated. I know it's just a game, but when it finally stops erroring and ATC comes back and they scold me for "being off course" when I'm actually not and it's because this error prevents the game from seeing me hit the waypoint, it makes me want to put my fist through the screen!I am currently flying... this error has appeared twice during this flight... after repeatedly clicking OK on the error message I have been lucky that RC has come back. I will create a log file next time I fly and hope it happens again. Otherwise is there anything I can do in the meantime?Thank you, Matt

Hi Mark,How would I go about checking the log? Where do I find it?I called Jetline. They had me try a program called Passmark to check the performance. I didn't do it with them on the phone, but I just did it now and EVERYTHING passed with flying colors, including the video card and CPU. So I am hoping it is a heat issue. I know there is a switch for a cooling fan. I just check it, it was on Medium so I bumped it up for High and will try some flights and see what happens.Thank you everyone for your input, I hope to not have to come back for more answers!Matt

Here are my system specs:Operating System: Windows XP Home Edition SP3 (32-Bit) Motherboard: Nvidia nForce 750i FTW SLI, PCEe X16 2.0, 1333MHz FSB Processor: 2.83GHz Intel Core 2 Quad Q9550, 1333MHz FSB, 12MB CacheCPU Cooling: Jetline Premium CPU Air Cooler System Memory: 4GB (2 x 2GB) Corsair XMS Low-Latency DDR2, 800MHz Graphics Processor: 896MB Nvidia GeForce GTX 260, GDDR3, PCIe System Power: 950 Watt Jetline Approved Multi-GPU Power Supply Sound Card: 7.1 High Definition Integrated Audio Primary Hard Drive: 300GB VelociRaptor 10,000RPM SATA 16MB CacheSecondary Hard Drive: 500GB WD Black Edition 7200RPM SATA 32MB CacheMedia Drives: 20x DVD Dual-Layer Burner w/ LightScribe (Primary)I clean the PC on a regular basis, including after the second time this happened. I bought the comp in December 2008, so I will be quite frustrated if the video card is giving out, but I might give a call to the company just to be safe.Matt

Hi all,So I have got a somewhat puzzling issue on my hands. The last few times I have flown on FS, it has crashed on me and I am not sure why. At first I thought maybe it was a one time glitch, but it has now happened 4 times. Here's my description of what happens:Playing FS as normal when all of a sudden the screen goes to a single color (like a mix of all the colors on the screen) and the audio makes a funny, repetitive noise. There is NOTHING I can do to resolve the glitch except to restart the computer. No keyboard commands work, it's like the computer has completely frozen.Now, the first time it happened I had just taken off from KSFO. Now I thought maybe it was an issue with San Francisco, but the second time it happened, I was on approach into KMSP, so I assumed it was an issue not just with SFO.The third and fourth times it happened, I was at KSFO again, taxiing to the runway and both times it happened as I was changing the view using my hat switch. I cannot remember if I was cycling views when it happened the first time.Extra background info would be that I am running Radar Contact v4 and AISmooth.Does anyone have any idea what is going on and how to resolve it? Obviously I am thinking a complete reinstall might help, but clearly I don't want to go through all that.Best regards,Matt

Hi all,I have built myself an overhead panel for the 757 and was in the process of assigning buttons and switches, but when I got to the PAX signs (seatbelts and smoking), there was no keyboard assignment for those switches on the PSS 757. To baffle me even further, the PSS 777 does have the PAX signs commands.Does anyone know if there is a way to add a keyboard assignment for the PAX signs? Any help would be greatly appreciated.Best Regards,Matt

Thanks guys. That all makes perfect sense but I was still just a little confused why it works for some planes but not for others, so that's why I asked. Basically you are saying there is no cure (besides flying closer to the normal rate) for this issue?Regards,Matt

Hey all,I was just wondering if maybe there is a remedy to this situation. When I do flights, especially long flights, I tend to use an increased rate of simulation. Anywhere from 2x-8x is usually what I like to do. Using 2x always works without any adverse effects. Using 4x usually works, but every once and a while the aircraft will randomly and erratically spin out of control until I return to normal sim, where I have to re-establish my routing. When I use 8x, it works for some aircraft but not for others. Examples; my PSS 777's work just fine at 8x (thankfully since transpacific flights take forever) but my PSS 757's do not. When I do 8x on the 757, it starts out fine, but then the altitude starts to fluctuate. It's mild at first; one hundred feet up and a hundred feet down from set cruise altitude. But it gets worse and soon the fluctuations can be a thousand feet above and below, at which point I clearly need to reduce the simulation rate.Does anyone know what is causing these fluctuations? I have adjusted some weather options using FSUIPC so that winds don't gust aloft and the rate of change isn't dramatic, thinking that maybe the winds were causing the issue, but it persists. Any help or insights would be greatly appreciated!Regards,Matt

I'm not quite sure what you mean. I am trying to merge the POSKY model to the PSS panel. As of now, I am using the PSS .air file for each engine type, along with the PSS .cfg file for each engine type, but in the .cfg file the "model" section is directed to the POSKY model for each type. Does that make sense?

Hi all,I did a search but was unable to find any answers to my own questions. I am trying to successfully complete a merge of the PSS panel flight systems with the POSY 757 model. I have been fairly successful by using the PSS .air file and the .cfg file and just the POSKY model file, except for a few things...1. My EICAS displays are not always accurateFor some of my PW 757's (not all, some of my winglet ones are accurate), the EICAS display is more like the RR models, with N3 included when it really shouldn't be. Even more strange, my DL and NW winglet models have the correct EICAS, but the UA variant (which is using the exact same .mdl file as the DL and NW) has the RR EICAS. Anyone have any idea why this is and how to fix it? The PW 757's are using the PSS PW .air file, in case you might ask.The second problem is the more troubling of the two...2. The merged aircraft do not respond to altitude or speed restrictions in the LEGS page.This is the main issue I want to solve. All the autopilot systems work just fine, expect the LEGS page. Until recently, I was not flying using SIDS and so it didn't make a difference to me on the LEGS page, so long as the VNAV climb and descent worked, which they did. But now that I have started flying using SIDS, it has become clear that this non-responsiveness to any input on the LEGS page is a huge problem. Does anyone know why the aircraft isn't responding? Does this have something to do with the PSS model? Is there any way to get this to work with the merged aicraft?I love the PSS 757 panel and the systems are modeled great, but the aircraft model leaves something to be desired. The POSKY 757 has the perfect "look" of a real 757, plus I love that I can add/edit wing views instead of the VC. If anyone knows how I might be able to complete this merge so that the aircraft is fully functional, I would be forever indebted to you. Any help is greatly appreciated!Best regards,Matt Armstrong

Bob,THANK YOU soooo much! I have finally figured out how to access the .WAV files and couldn't have done it without yours or Dai's help. Thank you so much to the both of you. I am sorry to have started such a commotion over legal issues with this thread, I didn't realize that by modifying aircraft that I have purchased legally for my own personal use (and no redistribution) could be such a major issue.Regards,Matt

I never intended to redistribute them, I just wanted to change the audio that is built into the GPWS of one of my aircraft. I didn't realize that it's not legal to even just edit them for personal use, but again I had no intention of redistributing.Thanks to everyone else for all the help as well!