Scarp

Sorry man, that was my bad, didn't see that this was in the fs9 section until now. I just followed one of the links from the front page. My suggestion is for fsx. :Whistle:

Look in the aircraft.cfg file, look for [CameraDefinition.***], find the camera definition you want to change and look for a the InitialZoom= line and put in the numbers you need, in your case it would be InitialZoom=0.6

Yes, you can dial in the speed manually using the FMC/MCDU, go to the decent page and put in numbers there. There's supposed to be a update for the A320 package soon which addresses that, but for now, just type in the speed in the performance/decent page. Mind you, put in not only knots but also mach numbers. As far as I know, it doesnt have managed decent (vertical profile) yet, although it should hold altitude restrictions if there's any.

No problem my friend, I'm glad you got it sorted out.

First off, yeah, the PIT indicates that the pitch hold is engaged, and the green HDG should normaly indicate that it is activated. And when you hit the NAV it should correctly show a white LNAV which indicates that the LNAV is armed. Normaly it would turn green when you intercept the programed flightpath. Same goes if you were flying to intercept a VOR radial. But if nothing works, a reinstall could be the solution. Obviously something's missing if all indicators tell you that they are activated, but nothing happens. Just remember to run the installer as admin since win7 is notorious in the f-it-up department when it comes to it's build-in "safety measures". I have personally turned it all off and taken ownership of all folders + I run the whole shebang as admin lol. So my win7 runs more like the good ol XP in that regard. Never had a file secretly arrested by win7 since then.

No problem. As far as the heading function goes, it should work regardless. In fact you can even arm the heading control on the AP before you turn on your AP, it will then automaticaly engage hdg mode once you activate the AP itself. So I must admit, it does sound kinda strange that it doesn't engage. You should pay notice to your left PFD because all AP functions you arm or engage will be displayed in green letters along the top edge of the display. First of all you should confirm that when you turn on the AP that the green light on the AP button itself is lit, then check you left PFD where it should be a green AP present. Same thing with i.e when engaging hdg mode, the light near the button should be lit green and the PDF should say AP and HDG with green letters.

Hi there, I dont have the 777 but, I experienced the same issue recently. It didn't matter which addon or where in the world I was flying. After googling and searching forums, I was still stuck. So I found some German forum and tried to use google translate but the result was more greek than english. Btw, here's the link for those that do understand german: http://www.netzblogr.com/loesung-fuer-den-r6025-crash-in-prepar3d-und-fsx Anyhow, make a short story long, I did get that they were talking about some dll's in the windows\system32 folder, so I decided to check if the same ddl's were present in my system. And they were, so I made a backup folder within the sys32 folder and moved the dll's to the backup folder I just created. Lord and behold, now were back in business again and the sun is shining, birds are chirping and I can hear childrens laughter somewhere in the distance. The dll's to look for are: msvcr100_clr0400.dll, msvcr110_clr0400.dll and msvcr120_clr0400.dll So if you have this problem and tried everything else, then have a look inside your windows\system32 folder, the perp may be hiding there. NB! Never delete these kind of files, either rename them or move them to a backup folder, just in case if you should need them again. Disclaimer: So far I haven't noticed anything negative by removing them, but what ever you do to your own computer is your own responibility. I looked at it like this: if the only option left was something as drastic as to reinstall FS and maybe even the OS, there's no harm in trying....and so I did, and it worked, saved myself a whole lotta trouble.

Thanks dheyer, hope it helps any frustrated ERJ pilots out there, this is truly a gem of an addon and she's still one of my favourite planes that I never get tired of flying. I mean, good visuals (even the VC despite it's age), pretty indept systems and a joy to fly by hand...what more can you ask for?

Here you go.....also, since we're in public space I wrote this in general terms to hopefully be of benefit to most readers and I've skipped alot of smaller items and completly focused on the core essentials for a FMC flight. Btw: I noticed you said you loaded a flightplan in your attempts, I assume that it is a FS flightplan you loaded? If so I must admit I have never tried that function myself, I always enter/program my flightplans directly in the FMC, just as we are going to do now. It realy doesnt take much time anyway. If I remember correctly you can also save the flightplan in your FMC for later use. 1'st off, like in all aircraft equiped with a FMC, it is important that it's programmed correctly. So let's quicly run through it. I made a short flightplan between Denver (KDEN) and Aspen (KASE). This is the flightplan: KDEN ELORE V356 DBL KASE -------------FMC---------------------------------------------------------------------- So without further adue, let's open the FMC, hit the position initiation button and choose KDEN. Then hit the LSK where it says FLT PLAN. By now, your departure (KDEN) should be displaying where it says ORIGIN. Now enter the destination which in this case will be KASE. Next we'll add our route, which in this case is deliberatly short but also contains airways so I get to demonstrate how to enter them into the FMC. Where it say's VIA.TO, we enter our first waypoint which is ELORE. From ELORE we are going to follow the airway V356 to DBL, so for the next VIA.TO we enter V356.DBL. Now you'll notice that all waypoints between ELORE and DBL is automatically added by the computer, to our flightplan. In the last VIA.TO we enter our destination: KASE. Now let's check in with ground control and get the active RWY (or just choose whatever you like if you dont wanna mess around with FS ATC). I got RWY 34R, so let's hit the LSK where it say's DEPARTURE and select RWY 34R. If you dont see it on the first page use the PREV/NEXT buttons to switch pages until you find 34R listed. When you select RW34R, the next window that pops up will be the SID page. This is where you normally would select a SID but since I dont have any charts we will skip it for now and just head straight for our first waypoint after take off. So just hit ACTIVATE, and we should be back to our flightplan page. And this pretty much conclude our fligh planning. Now we need to tell the FMC about our plane, so hit PERF INIT, use the NEXT button to switch through the pages, in our case we are only concerned with pages 4 and 5. On page 4, since we are in US we dont need to change the TRANS ALT as it is set for FL180 by default. In Europe however, you'll have to change it according to your local regulations. Next I usually also enter my cruisealtitude where it says INIT CRZ ALT, and by looking at some freeware maps it looks like FL146 is the minimum altitude we should use, and also note that the approach to Aspen starts at FL130. So let's just make sure we have some distance between us and the rocks below and go for a cruise at FL180. So enter 180 into the scratchpad and press the LSK corresponding to the INIT CRZ ALT. Quick note: The performance pages are important in helping the FMC to better calculate flight performance and fuel. Next, switch to page 5 to enter aircraft weights. This one is rather self explanetory, so when you've entered all relevant data, CONFIRM INIT should be displayed in the lower right corner of the FMC. Confirm by hitting the LSK. General Tip: At this point, the FMC may give you warnings based on it's own calculations derived from the data you entered on the PERF pages. For example, if you set a cruise alt that is too high compared to your aircraft weight and performance data it will let you know. If you do get a warning, then just lower your cruise alt on page 4 in the PERF INIT pages until it stop's pestering you. Now hit the FPL button on the FMC to take us back to our flightplan, we should now see that both speed and altitude data has been added to all the waypoints along our route. Now since this is a crash course, we can just go ahead and add our arrival data as well. I usually enter it towards the end of the cruise leg when I can get the most relevant met data as well as approaches and active rwy's. But for this "tutorial" we'll assume to know that we'll be landng on RWY 15. So, hit the NAV button and choose ARRIVAL by hitting the LSK next to it. Press the LSK next to RUNWAY and select 15, and the APPROACH page should automatically pop up. Next we'll choose the LOC/DME-E for rwy 15 by pressing the LSK next to L15-E. Hit the LSK for ARRIVAL and we're back to the main ARRIVAL page and hit ACTIVATE. This should bring us back to the flightplan page, use the NEXT button to scroll to the end of the flightplan where we'll find a DISCONTINUITY. To close the flightplan we first press the LSK next to RW15, that will make RW15 pop up on the scratchpad, then hit the LSK where the open VIA.TO is. And that's it, we've done the FMC and now the plane knows where we want to go. -------------Cockpit------------------------------------------ While we're at the gate we'll just do some cockpit preperations too, first we tell the airplane to use the FMC for navigation by pressing the FMS button on the DCP panel*. That should change the color from green to magenta on your PFD's. Next we'll dial in our assigned altitude in the AP, in our case we'll just set our cruise alt straight away, but normally you'd enter whatever clearence you got. But that is not important for this lesson so just dial in 18000 and turn on the flight director by pressing the FD1 button on the AP. --------------Flight-------------------------------------- With the FMC and autopilot configured, fire up the engines and taxi to the rwy. *Line up, sync your AP HDG with the RWY and off we go. *When you've taken off, cleaned up the aircraft, engage the autopilot (AP) and then press HDG (note: if we had entered a SID, we would hit the NAV button instead of the HDG button). *Accelerate to 180 kts and hit the SPD button. I think, but dont quote me on this lol, but I think I remember that the best rate of climb was 180 kts for the ERJ, so that's what I'll use. It really doesn't matter for this tutorial anyway. You can use the FLCH function too, it will keep your speed below 250 under FL100 and accellerate to 270 above FL100 (or whatever numbers you've entered in the performance pages). But anyhow, now we should be climbing at 180 kts on the rwy heading (or following the SID if we had one), because we do what we want in this "tutorial", we get a imaginary clearence to turn left to a heading of 220 degrees to intercept our flighplan. *So turn your HDG indicators to 220 and the aircraft should be turning left to the new heading. While we are coming out of the turn, press the NAV button in order to arm it. Note: you should intercept a course at less than 30 degrees. *The aircraft should turn automatically from HDG mode to NAV just before we cross our intended flightpath and bring us on course with the flighplan. *Now we should be happily cruising along our airway at FL180. If you zoom out on the right PFD you should also see the calculated TOD somewhere between DOBEE and FIDLE waypoints. Anyhow, I'll end my mega-fantastic tutorial here since my sim decided to to have a virtual funtion call and CTD'd on me lol. But there isn't realy much too do from this point except watching your airspeed and initiate the decent whenever it's time. I would like to add, that this addon is rather well simulated in terms of systems and there's alot more under the hood than what I've barely touched upon. I just swung by the absolute minimum but essential steps to enable a LNAV flight with the FMC. If for some reason it doesn't work, you better call Huston and tell them you got a problem XD because I honestly wouldn't have any clue as to what could be wrong. It could be everything from the mundane "install as administrator" to maybe a defect or missing VB runtime installation etc. Because as I mentioned earlier, I have never had any issues with the plane(s). But I am crossing my fingers and I sure hope it works out for you. *DCP panel are the two identical small panels just right and left of the autopilot on the glareshield

Sorry for the delay, work and sleep got in the way. I'll write a short tutorial, just give me a sec.

I can truly tell you that I have never had any issues with neither v1 or v2 of the Embraer jets, it is a 'fiddely' little aircraft with a certain logic to it's systems. Just like Boeing and Airbus have their system logic set up differently. So that means you have to take the right steps in the right order, or else....... :o And I know from experience when it's been a long time between flights, I forget certain points in the flow, then things tend to get messed up and I have a D'OH moment when I remember that I forgot this or that. So yeah, she'll pretty much ignore you if you ignore her....and her needs I can write a tiny, highly unscientific, totally basic A to B "tutorial" of which butttons to press at which stage to enable a safe LNAV flight if you want.

Yes, it's supposed to do that. If you did that, and activated the FD, the plane should now fly according to your FMS flightplan when you engage the AP + NAV button. I am asuming you have programmed a flightplan and that there's no errors in it, threw in a SID (if applicable) and that you can see the flightplan displayed on the right PFD.

Very hard to say anything exactly based on the limited info you provided. To that end this suggestion is a stab in the dark: Did you press the FMS button on the DCP before hitting the NAV button on the AP? (DCP are the two identical small panels just right and left of the autopilot on the glareshield). Although the DCP is a 'display control panel' the 2 buttons in the upper right hand corner (NAV and FMS) are the actual buttons that tells the AP which source to use. So if you want the plane to follow the FMS you gotta hit the FMS button on the DCP before you engage the NAV function on the AP. And vice versa, if you want the AP to follow VOR's you hit the NAV button first, followed by the NAV button on the AP itself.

That can happen if airways or intersections have been revised or changed. So if you are using an 'old' flightplan with a new (and changed) nav cycle this can happen. What I do when this occurs is to program it manually, depending on what has changed in the new cycle I just throw in a 'direct to' between the point's affected. If you have a flightplan where all nav data between waypoint -> airway -> waypoint is available/listed, you can manually insert all the nav points one by one (as direct to) and skip the airway all together. To avoid manual labour you'll need to create a flighplan using the same cycle as your MCDU (FMC). So it has nothing to do with a special aircraft but all to do with mismatching nav data. And just to add; the nav data is revised every month. Not that all nav points are altered monthly, but changes here and there do occur. Hope that it helps alleviating your frustrations.

They both work together. The ENKR photoscenery from AoN is a hi res photo of the airport while the AoNN photoscenery is covring the rest of the area. The Batsfjord scenery from AoN is just the photoscenery to my recollection. The AoNN contains custom 3D models. They too are made to be used either together or separate. Should you by, any chance discover anything double at ENBS, check that all AFCAD files with the prefix ENBS is deactivated within the AoN folder.

If you are looking for a turbo-commuter I'd spend my money on the Saab 340 instead, I was very disappointed with the ATR and parked it for good after 1 flight. None of the two has any sophisticated NAV equipment, on the other hand, the s340 doesn't pretend to have one either as the early s340A's only had basic VOR/NDB equipment unlike the later models which had a FMC. The ATR uses the default GPS instead of a proper FMC and there's no other system simulation of any depth. You jump in and fly (as advertised) and that's about it. Personally, I am not too impressed with the VC either, to put it this way, the s340 has everything the ATR doesn't. Also a higher price but it's worth it (compared to the ATR).

I'm a BBS driver, not going into any arguments, but, the BBS 320 package contains all models from 318 to 320 with the 321 coming in the next update. They also contain all engine configurations so there's a whole bunch of models wrapped up in one package. And it works in FSX, P3Dv1 and v2 and you can have it installed in all the sim's. As far as systems go, this is the closest thing you get to airbus as of today. And updates have been coming on a regular pace up until one of the two developers lost his wife last summer. Considering that they are only two guys working on it, plus the unfortunate happening last summer, I think the guys are doing well as far as updating the project. Next update will contain not only a 321 but also a brand new VC plus further systems updates and implementations. As far as the "they should finish the 320 first" argument is a moot point in my opinion. What is time consuming in aircraft development is system programming and not necessarily 3D modeling (without detracting anything from that process, I'm a modeler myself). And consider that the airbus systems are much the same over for all aircrafts in a series, I'm certainly not crying my heart out because I got a bunch of different models in one neat package.

Ok, then it's back to basis, going to need some more info of your setup. 1'st off, do they work at all, as in other aircraft but the ERJ? It is hard to say 'what' it is based on what you've told, but if you are sure they are assigned to the axis, it might sound like there are some double assignments of the throttles somewhere down the line. Are the controllers assigned through fsx settings or did you assign them through FSUIPC? Or both? Please check all the relevant controller setup interfaces in both FSX and FSUIPC, remember to check both axis as well as button configs to make sure you don't have any double agents, that's like asking for trouble. Only have one or the other, not both. Did you manage to calibrate the throttles (in FSUIPC)? To do so, open the FSUIPC interface and open the "Joystick Calibration" tab. The rest of the process should be quite self evident. At the throttle page, pull the throttles fully back and press the left 'set' button, and the full throttle and press the right 'set' button. If you have idle detents on your throttle you can put the throttles into the detents and press the middle 'set' button. In the FSUIPC axis assignment tab, when you move a axis or press a button, it should automatically display the settings for that particular axis/button. If any are assigned that is, if there aren't you wont see any difference in the FSUIPC interface. And if you find anything, you have to press the 'rescan' button to make a new scan (i.e trying a different axis/button).

Sounds like you assigned the throttles to button-commands instead of the axis/slider commands, that's my guess (based on all the available information).

My vote goes for the BBS, as mentioned it is a WIP, but so far it is the best airbus simulation on the market. Add to it, you also get the whole range from A318 to A321 (although the A321 has not been released yet, I suspect it will be part of the next update).

I thought you only had to change the texture resolution (through the menu) and then switch back to whatever resolution you were using originally?

Found mine at C:\Users\Administrator\Documents\RAZBAM\Manual

Are sloped rwy's facilitated in any way shape or form, or is it still the "flat world" as in fsx/P3D v1? (not the whole world obviously, but the ancient flatten around the airport and boundaries)

Of course I'm not wrong, and certainly not very wrong, how dare you. He asked "Can anyone comment on the very annoying FSX bug that is the "dynamic" head movement?" That was what I was replying to. Dynamic head movement is what it is, an effect to simulate the dynamic visual feel of...the dynamics of flight. On the other hand, you are right about the rest, 1'st that we were clearly adressing different issues, and it's an issue I havent noticed since I dont fly longer flights than 4-600 nm, and my flights mostly takes place in a very limited area flying routes along latitudes across a rather small patch of our globe :lol: But I did as you suggested, and it (the view) did change slightly. Kinda funky since all data related to head position is defined, as you said, to the center of the aircraft model and not coordinates. Well you learn something new everyday. But that leads to another thought, if the viewpoint shifts, what else tied to the aircraft CoG shifts possition, lights (assuming they are effects and not 3D modelled), location of fueltanks, cargo etc? :rolleyes: But I was never wrong, and certainly not very wrong. I might perhaps maybe, for the sake of argument, agree that there was a misunderstanding if that brings closure ^_^ Note to self: never fly diagonally across the globe, you might fall off the plane :lol:

In that case you have installed something that provides dynamic head movement other than default. And what 'that is' only you (should) know Have you, or have you ever had EZdoc installed, or fsrecorder? Accusim? Or any other addon that produces dynamic movement? I have none, and I can assure you that my virtual pilot's head is rock solid. The above fsx.cfg entry was copied & pasted directly from my own current cfg. B)