darth_damian_000

Thanks for your reply. Currently, I have REX 4 - Textrure Direct Build 4.8.2016.0210 with softclouds.

Tell me if I understand this correctly: On the Audio Control Panel, if I press the fourth button from the left (MIC button lights up), I will be talking to the ground crew? (will I also need to have the right frequency on the radio panel?) If I press the 5th button, I will be able to speak to the person at the flight attendant station? If I press the 6th button, I will be able to speak to the passengers? Does that necessarily mean I will be able to hear them, or do I need to enable the monitoring for these places as well?

Real Environment Extreme (REX) released an update about 2 months ago. I am finally going to download the 7GB lump but how do I go about actually updating it? Do I just run the installer? Do I have to delete the old one? I don't want to face any licensing issues. Thank you

Well, I found my own answer. For those who want to know: 1) The version is on the menu bar on the add-on drop down menu. I asked this question because my SODE came by default with Drzewiecki Design UUEE. I never directly installed SODE, and this is possibly why this version wasn't displayed. 2) There probably is no way to uninstall SODE because of the way I obtained it. After installing it, the installation process removed the old version for me, and installed the new one. 3)http://sode.12bpilot.ch is the website, and there is a downloads tab from which the installer can be obtained. The reason I had the verification issue is because only about 3.3 MB of the file was actually downloaded (as in, the download was completed, but the download manager didn't retrieve the entire file size, which is about 6.7MB, as indicated next to the download link. Hope this helps!

I have an issue with jetways from Drzewiecki Design. I contacted the company, and I was asked what version of SODE I have. 1) How do I check what version I have? In any case, it seems I am supposed to have the latest version, so I nonetheless tried to install a new one. I am told I have to uninstall the old version, but, 2) How do I uninstall my current version of SODE? I don't have it in my program files, and in the P3D directory, I see a SODE folder, but no uninstall .exe files. I still went on some website to at least download SODE (http://sode.12bpilot.ch/) but when I download the file, windows is preventing me from running the installer because it's unverified (I ran it as admin). 3) How can I download the new version of SODE? Thank you.

My rule of thumb is...check the runway elevation on the LEGS page. Add 4000 feet to that. This is the altitude at which I want to have my flaps extended to flaps 1 (v ref + 5 + 80), and then work your way down speed-wise. Another thing I follow is at 40 miles away from the airport I want to be at 10000 feet flying 250 knots (a common restriction as you know). If at any point the plane can't slow down, I use spoilers. Hope you're enjoying the 777!

If it is just slight, then maybe it's just the effects of the taxiway. Depending on the scenery you're using, maybe the bumps that exist on the taxiway cause the nose landing gear to slightly deviate. It could just be an effect of realism, and you can easily correct this by responding with the appropriate tiller control. You can also try recalibrating your joystick. I find the keyboard an annoying way of controlling the plane. Pressing a key once doesn't do anything, but holding it for just a tenth of a second will make the movement too drastic. Hope your issue gets resolved

I know that the aerosoft airbus has a ton of annoying views, many of which don't allow you to pan the camera. I'm going to bite another add-on bullet and get EZ DOK, now that it is seemingly available for p3d. Do you heavily use the radio when you're simming?

That's right. The problem is that the textures are ridiculous. Everything seems fine when my view in the cockpit, or when it's a bird's eye view (although in this case I suppose its more accurate to call it a "international space station view") of the airplane and the scenery below it. The problem is this: When I cycle through camera views (I know, I know, I'm getting EZ-DOK soon), I will eventually end up on a view from the nearest tower. Once that happens, the textures go blurry. Like if the ground has grass, then the entire ground turns green (with a few houses sticking up). Similarly, the ground turns tan when I am over a desert. When I switch to a cockpit view, the textures look blurry and don't seem to want to reload after a few seconds. HAH! The way they replied, and from the responses I received here, it seems like it is a grasping-for-straws situation so that I keep vector, but even if I do they still have my money :[

I got a message saying that my RAAS Professional is out of date, and I have the option to update it. As you all probably know, you are directed to a website and...I have two options, and it seems like I can only choose one, based on the language they use. I have both aerosoft and PMDG add-ons that use RAAS and I need to know how I can go about updating this. Thank you.

I appreciate the input I received thus far. My stance on "tweaking" is conservative, as in, I don't want to tweak unless I really really have to. I never opened the CFG file, until today, and I didn't find these lines, so indeed that is not the issue. The only thing that has changed since last startup is.....I installed new livery to my aerosoft airbus, and used it during this flight. I will do more research, hopefully to come up with some sort a solution. Thank you for your responses you guys. This is such a helpful community. EDIT: I had issues at KDFW. There was an elevation issue, where the parking space where my plane was essentially sunk below the airport. I had to use the Vector Configuration Tool to add the airport to the list of exclusions where ftx vector has an influence on. Could this be a possible cause?

Up until recently, I had no issues with textures. Now, all of a sudden, I am getting them. I asked about it on the ORBX forum, and they advised to "remove jobscheduler affinity mask" in the p3d.cfg file. Can anyone tell me what this jobscheduler affinity mask do? how is it vital to my simulator, and what is going to happen if I remove it? How do I remove it anyway (change a value, delete the line altogether?) It seems relevant to say that I have an i7 hyperthreaded quad core CPU. Thanks you all!

Ahha, you nailed it. It was flight that I saved and loaded. So when I started the flight (2 days ago), the cruise altitude was set to FL380 as planned, and it remained at 380 all throughout (at this point, I didn't pick an approach yet) on the FMC. I had to leave, so I saved the flight, and reloaded it when I was able to fly again. I just loaded that flight right now, and the FMC values were changed. For example, I was to be at FL301 at the BCE VOR (which is the 2nd waypoint behind T/D), whereas when I plugged in the Approach (BEFORE I saved the game), it was FL380. The FMC values changed after loading the game. I also saved the panel state under the same name as the flight, and the values remained the same (as in, FL301, and yes, this is all BEFORE the top of descent). Is this some load flight issue? I don't use hardware throttles. I disabled the throttle axis and I just use autothrottle during flight and the F keys if I have to take off / land (reversers, idling) I will fly it tonight, as a refresher perhaps.

This happens a lot, but I will use one particular flight as an example. I am flying from KORD to KLAX on a 777-300ER. I am cruising at FL380. My AIRAC is 1605, and I am going to take the RIIVR2 approach to land on RWY25L. Just after the HECTOR VOR is my top of descent, and after that, a waypoint, GRAMM, had a restriction: FL210B / FL170A. GRAMM is 74nm away from the airport. Once I get the "RESET MCP ALTITUDE" message, the plane, I set the MCP to FL170 and NOT press the selector. As I pass the T/D point, the plane does not descend (to be honest, the plane never automatically started to descend, I always had to push the selector). Mind you all, LNAV, VNAV, and A/P are all on. When it does descend, I am at FL170 at GRAMM flying at 280kts (is this normal?). On another occasion, I pressed the selector 2NM before T/D, and the plane failed to descend to FL210, instead, it was descending at a very slow rate. At GRAMM, I was at FL260. Any reattempts were performed after shutting down P3D, and reloading it at a save point about 40nm before the HECTOR VOR. So I learned, and started to use V/S and speed management (with spoilers) to plan a safe descent, and it has worked very well for me. I would appreciate if someone explained to me these two things: 1) Pertaining the the given scenario, I want to descend to FL180 by the time I reach GRAMM. My goal is to reach the speed of Vref(+5) + 80 at 4200 feet. So on this initial descent, how fast can I allow the plane to fly, so that I safely lose speed throughout my descent? I would like to stop relying on my speedbreaks. They are an important component and but by now I was hoping I can make it through a flight without a CAUTION warning. 2) Again pertaining to the last scenario, am I having issues with my autopilot? After all, it doesn't start to descend at T/D after the MCP has been reset, and furthermore, the speeds are ridiculous as I try to reach the GSIA (glide slope intercept altitude). Thanks for your time and help!

My usual method is to change the altitude setting in the MCP with the GSIA and press the selector BEFORE T/D. This is possibly removing some pre-programmed constraints/restrictions, which is why I probably have to play catch-up to get the right speeds at the right altitude, usually done with V/S. This may be off topic, but what makes you decide whether to use V/S or FLCH to correct your descent?

LNAV and VNAV are all ON, speed window in the MCP is blank, AT on at all times (including landing). Yes, I do monitor the vnav path in the ND, and most of the time, I find myself above the glide path. my problems begin when I need to go away from vnav and enable vertical speed mode, which in turn, speeds up the plane. To combat that, I later have to enable speed mode and I attempt to slow down to vref + 80, at which point, plane requires drag. I use say, half full speedbreaks, and I get a caution alert. cool. i arm speedbreaks and...I'm speeding up. That is basically my story. So I am doing something wrong. I do appreciate your input and I will take a look at the FCOM. Thanks for the advice. I will most likely fly again, stress less about it, and see how it goes. I use F1-F4 to control throttles. I am not doing anything, as A/T is on at all times.

A good indicator to fly by, thanks!

Hello everyone. Life story: I am struggling with flight simming itself, specifically the landing, and I would like to ask you all for help and advice. My problem is rather simple: I am unable to land manually, and if I am, then my plane is all over the place. I would like to get to the bottom of this issue, and I am getting back to the basics. I was taught to set the MCP altitude before T/D at the G/S intercept altitude. As a result of this, I almost always have to go into vertical speed mode, because I will not be able to reach altitude/speed restrictions along the descent path. The problem THEN becomes I am descending too fast, I am picking up speed, and I have to compensate for that with spoilers, which is undesirable for me as I would prefer to last through a flight with minimal warnings (hah!). Anyway, I would like to know if my initial altitude setting philosophy is plausible, and if you could identify any issues in my little rant, I would appreciate the criticism of my skills (yup) and even moreso a solution. Secondly, I would like to ask what does what exactly does the MCP altitude selector do? In the instructional video, the narrator set his to 7000 feet, didn't press the button, and the plane started the descent. Upon almost reaching 7000 feet, he reset the MCP altitude to 2000ft WITHOUT pressing the knob. Would it make a difference if he did press it? Is there even a difference between a situation where you set MCP to 7000 and then again to 2000 as opposed to setting it 2000 right off the bat at T/D? Thank you for taking the time to read this, and providing me with any help to improve my flying. Props to PMDG for making such amazing products.

I'm planning on getting a new SSD, and I would like to know how would I transfer all of my orbx products (global base, vector, open lc europe and Alaska/Canada), so as to preserve my license. Thank you.

Can I use this tutorial to update an existing version of ASN?

Thank you for your contribution to this forum. I really appreciate the help, and I am looking forward for more tutorials.

Does uninstalling scenery affect ORBX files? How do you do this exactly? How do you reinstall FTX global, without having to purchase the license again? Also, did you have to reinstall all FSDT airports / products?

I followed a guide on this topic to update my P3D. The process involved deleting some programs from the add/remove programs feature of the Control Panel in windows. Those were "client, content, and scenery" but I opted to only uninstall the client, and then download a ~150MB file from my p3d account page. Things SEEM to work fine. But now, I am unsure how my add-ons have been integrated. For example, I cannot get the GSX window to come up. I read I now have to uninstall the "content" part of p3d but it may override my FTX scenery. I am lost and confused. I have some computer knowledge but I always fear losing my add-ons when I play around with these little components of p3d. Many of these add-ons scare me, saying that they are allowed only for one time use on one PC only. Can someome link me to a guide that will simply uninstall p3d, reinstall it, and keep all of my add-ons as they were, without having to purchase new licenses? Thanks for your time and understanding.

Will the add-ons remain unaffected? Among airports, I have orbx global and vector, as well as ASN and REX.

Here's the deal: I pick my airport, gate, plane. I hit "OK" and the game crashes. No windows error or anything. Just goes back to windows. I recently did an update from 3.0 to 3.2 using the install client method, meaning, I installed the ~150MB file from the p3d website, and just installed over my current version. I did not uninstall the game, as I fear that all of the add-ons that I have will be void, as many developers say ONE PC ONLY in their policy. Any tips or suggestions? Thank you.