lonewulf47

Oh well, THIS is the important piece of information that was missing ! There have recently been a number of reports with that Fall 2017 (build #1709) update causing several problems. We will have to wait until MS comes up with a solution or - the second possibility - revert to the former build (#1703 I believe).

Same here, no issues at all. Running P3D V4.1 from the beginning and never had any issues with SimpleCam - also no issues in that respect during Betatest in FSL where I used SimpleCam all the time.

Hi Dean, Have you also reinstalled SimConnect? On P3D installs this is usually missing. SimpleCam will not work without that. Another issue could be missing access rights. You need to run (and also install) P3D AND SimpleCam with full admin rights.

Well, I do use SimpleCam with all my A2A planes and I haven't come across the observation you mentioned. In all my installs all 10 assignments work within the VC without exception - and yes, you are corret, the "0" (Zero) key of the numeric keypad can be used as a stored view just like all the others. A2A does not use specific key commands other than the standard SHIFT-(numeric) calls for the 2D-panels, but these are for the numeric keys on top of the keyboard, not the separate keypad. Difficult to say what happens on your machine when you press the "0" key... As Urs suggested, maybe some old and forgotten settings in FSUIPC?

In addition to what Urs said, please remember that you can only store a CAMERA POSITION, which is achieved by moving the CAMERA by the assigned keys - and NOT a VIEW POSITION, which is achieved by moving the view by the Hat Switch. Those are two completely different things and often mixed up. This is clearly explained in the manual. Furthermore please check that you have the <show information 'camera setting copied'> enabled in the configurator and that this message REALLY POPS UP AFTER USING THE CTRL+NUM keys. If it doesn't it is a clear sign that SimpleCam is not properly configured. And once more: as far as Prepar3D V3.2 is concerned, make sure that SimConnect is properly installed (explained in a post further up), as P3D is well known for missing SimConnect installs in various cases.

Hmm, I'm definitely running out of ideas... I just tried on two of my installs and couldn't see any misbehaviour of SimpleCam. I can still change all Cam Positions at will and store them (and subsequently of course recall them... ). Do you have the storing message activated and does it pop up upon storing position? (in fact it should ALWAYS pop up whenever you use the CTRL-+<numeric key> combo).

At this point we might need to do some basic troubleshooting first. - what OS do you use? - when starting P3D do you see the message that SimpleCam has loaded (lower right corner), just prior to the GUI popping up?

No, the assignments of the keys is stored outside of the "standard.xml" file. The modification of the "standard.xml" when using the "delete key assignments" button only removes eventually assigned commands to the numeric keys inorder to keep SimpleCam operations free from double assignments. SimpleCam itself does not make use of the "standar.xml" file at all.

Difficult to say where the culprit is without knowing the exact installation details on your end. I use SimpleCam on three different machines without any problem. FSX and P3D V3.2 on one machine, FSX, P3D V2.6 and P3D V3.2 on a second setup and FSX and P3D V3.2 on my laptop. All without the smallest glitch. So I severely doubt that this is a program issue.

No problems here. I see it closing all the time, even most of the times after a crash of FSX/P3D. The only reason I could imagine is that there could be a conflict with UAC settings and/or Installation as Administrator. You should have the UAC set to the lowest level and the checkbox in the Properties Box set for "run as administator". Other than that I'm a bit at loss. Maybe someone else has another suggestion?

Have you ever tried? Actually it should work to some extent when you rename the *.SimpleCam file with the new *.air name. Maybe it will need some finetuning, but normally PMDG has the center of the VC quite nicely equalized. If I remember well, I have done that also for the PMDGs. Just make a copy of the B737-600.SimpleCam file and rename it B737-700.SimpleCam or even B737-700WL.SimpleCam if you want it for the Winglet version.

Not that I knew. The reason is obvious: everybody has his own preferences and therefore no two camera settings would be the same. As I have seen during public applications even the default setting for start-up varies from the "5" key for default forward setting via the "1" and the "4" key. So you see, not even the basics are kinda "standardized" within the human brain... . This is however one of the great advantages of SimpleCam. Everybody can use it to his very personal liking!

Yes, I can confirm that on my end there are absolutely no problems using SimpleCam on P3D V3.2. One suggestion though: Prepar3D is well known for missing and/or corrupt SimConnect installs. It might be helpful to repeat the SimConnect Install. It's quickly done and will not harm an existing install, but possibly repair it. Just go to the: \Prepar3D v3\redist\Interface\FSX-SP2-XPACK\retail\lib path and run the SimConnect.msi installer. Maybe this helps.

Hi Ken, Are you sure you moved the CAMERA with the distinctive keys and not the VIEW with the HAT Switch? I can't see any anomality on saving camera positions within P3D V3.2.

Hy Anty, Not at all. The selection is based upon the aircraft model which basically means that all settings are used within the same model i.e. all models that use the same *.air file. So if you have many liveries in the same model folder they will not require a new setup. Even more so if you use the same model on different simulators, e.g. if you have Prepar3D and FSX (:SE) on the same computer, you will not even need to use a new setup on these. Also if you happen to uninstall and later reinstall the same aircraft: the settings will also be preserved!

Ken, Be careful when using external views with the VC cam. The external VC model does in no way correspond to the full model that you are going to see if you chose one of the simulator's default outside views. Depending on the manufacturer the "outside VC model" can be very rudimentary as it has only to cover the parts visible from the cockpit. With regard to your remark " ..the P3d choice setting on the configurator which appears to be required each time you open it ..." I too don't understand what you mean with that. There is no such thing like a requirement to use any of the four tabs as long as you don't plan to change the standard key assignments of your standard.xml - and usually you do that once and leave it that way. The function of SimpleCam is in no way affected by that. It simply works with the simulator you have running. There is no preset to a specific simuator necessary. Dont' forget, it's "SimpleCam". It keeps things simple...

To make things even easier: the manual can be found where usually manuals should be stored -> in the Documents Folder (a manual is a document, isn't it ): C:\Users\"username"\Documents\AivlaSoft\SimpleCam\Manual

Yes, this is an old and well kown bug on all FSX and its derivatives in all Virtual Cockpits. There was some discussion about this topic in several forums like here: http://www.fsdeveloper.com/forum/threads/head-drifting-in-vc-in-fsx.425421/ I haven't tried it myself but I guess the proposed method of setting the MomentumEffect = NO in the cameras.cfg should eliminate the effect. There are various explanations of the origin of this effect, but finally nothing to be absolutely sure about. IMHO it stems from a slight difference of the center point between the A/C model and the VC model.

Hi Graham, The NavDataPro Installer should actually point automatically to the correct installations path. The path window should look like this: "\AivlaSoft"

David, I can give you at least one piece of confirmation: I use AIRAC cycle 1409 with PANC airport from Aerosoft and ALL RWYs and SIDs are shown properly. The entries in the "runways. txt" file are of course not present as the Aerosoft airport features the correct (new) RWY numbering. See the picture below: (I have checked it in both FSX and P3D V2.3) So it's pretty difficult to say which gremlin is causing the missing runways. I take it that you of course ran the "simulator scenery data update" option on the DataProvider. Regards

Hi there, Please observe forum rule 1) above. As this is an international forum, Posts should be made in English. To answer your questions: EFB can only read the frequencies that are contained in either the default BGLs, or within a specific AFCAD of the respective airport. Everthing else is not possible as you would not be able to tune the required frequency! So, if there is a discrepancy within the frequencies you should check your installation. BTW: RWY 17R has NO ILS! A practical means to update your default navaid frequencies can be found here: http://aero.sors.fr/navaids.html

I have almost all Carenados and I don't see any problems using the EFB flightplans in their GPS. The GPS part is mostly default although looking a bit different due to frequency tuning capability.

Just a question: why would you do that? No FMC/FMGC ever stores SIDs and STARs in its routings. I know that some devs made it available for their models as a goodie for the simmers, but it's by far not realistic.

You may want to read the discussion here: viewtopic.php?f=5&t=1540

I use various scenery.cfg files and only use the DB manager when adding a new scenery. Just run the manager with all scenery enabled and re-run if new scenery is added (again with all scenery enabled). Temporarily disabling scenery items does not hamper EFB operation.