brian747

Members
  • Content count

    306
  • Joined

  • Last visited

Community Reputation

3 Neutral

About brian747

  • Rank
    Member

Flight Sim Profile

  • Online Flight Organization Membership
    none
  • Virtual Airlines
    Yes

Contact Methods

  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    2 nm from EGLF rwy 06

Recent Profile Visitors

3,189 profile views
  1. Thank you for that. I tried it, but it had no effect on the movement. I should explain that I'm getting movement of the camera whilst the aircraft is on the ground, so perhaps it's not "cinematic" mode that's doing it? The unwanted movement continues, however. It's as though a heavy telephoto lens is gradually tilting the camera view downward, so that the view of the aircraft on the runway threshold gradually becomes replaced by a view of the ground. [LATER EDIT — FIX FOUND] Ah-ha!! I just went exploring to try and find additional options, and found the "Advanced" tab (I'm pretty sure I hadn't ventured there before). Enabling the "Track Aircraft" switch has at last caused the view to remain where I wanted it. (I'm not sure how the thing became un-checked in the first place, but hey...). :-) Many thanks, Brian
  2. Apologies for raising this: I really *have* looked, but haven't found the answer (and it has to be something simple, one feels...). 8-\ How can I completely and permanently disable cinematic mode? I seem to have managed it previously, but following a recent update it's back and won't go away..... :-( Many TIA, Brian
  3. The words that Keven quoted were "activated on a single computer", which is what I have — hence my question, since I have a concern that the requirement for holding CP's settings only on their servers does already suggest an excessive imposition of anti-piracy measures at the expense of user convenience: something which would be unfortunate, to say the least. > "Just curious, any reason you're hanging onto Windows 7?" <grin> Were it not so I would hardly have gone to the trouble of arranging the dual boot. ;-) (On a different topic, the red 'Interested in joining OVPA?' button on the OVPA web site is broken). Cheers, Brian
  4. I have a single computer. On it I dual boot into either W7 or W10, both of which have a copy of FSX installed. Obviously, there is no possibility of my using both simultaneously. Can I therefore run CP in both environments, or are you saying that a second license would be required for the same machine? Cheers, Brian
  5. In cinematic view, there was a noticeable slight twitching of the aircraft, which looked almost as though some random turblence effect (head movement? engines?) was creeping in. That effect in cinematic mode has also been remarked upon by a fellow Admin at my VA, so I thought it might be worthwhile mentioning it to you. What prompted me to do so now is that, further to your suggestion to disable Smooth Zoom and Static Mode, having done that I found that the twitching effect in cinematic mode was gone (although some shaking of the ground still occurs, but since it only happens in low views as the camera moves upwards I think that's probably a different problem?). Cheers, Brian
  6. Ah — thank you, that's very helpful. I wasn't using the zoom controls in FSX, though, I rather naughtily edited the file directly (whilst FSX wasn't running). <*cough*> 8-º > "...make sure you enable the "Disable Smooth Zoom and Static Mode" in the Preferences" Roger, Wilco, and all that jazz. :-) Many thanks, Brian
  7. Hi Keven! I'm hugely enjoying your great product! :-) The appearance of my ChasePlane views initially was similar to that obtained by using a wide angle lens on a DSLR (I only fly 744s, which look extremely distorted and unrealistic in that presentation). After thinking about this, I checked out <username>AppData\Roaming\Microsoft\FSX\Cameras.cfg and found that three ChasePlane cameras had been added to the start of the file, all of which had their InitialZoom figures set to 0.4000333000. <gulp> Which would certainly account for the "wide angle" effect that I was seeing. 88-) Using the formula in the second video to which you kindly directed us, I plugged in the figures for my setup and the answer came back that in my case a zoom factor of 1.5 was applicable. So I edited the camera.cfg file and simple-mindedly substituted 1.5000 as the InitialZoom figure in all three cases. On starting FSX the distortion had completely gone (I had to move the viewpoint back a bit to compensate, obviously). :-) So I'm not sure where that initial zoom fiigure of 0.4000333000 came from, but it certainly had the effect of making an aircraft the size of a 747-400 look very strange indeed! However, now that I have changed the InitialZoom figures for all three types of ChasePlane view I'm finding that new presets added seem to inherit the figure from the previous preset, so presumably the problem has gone away. I just thought I'd mention it in case others had the same experience. :-) (Incidentally, does the "Focal" camera control have any bearing on this? It didn't seem to have any effect when I tried it). Cheers, Brian
  8. I entirely agree with the OP. Storing stuff in the cloud is all very well until there is some problem with the Internet connection. There should *always* be an option to store (and restore) a local copy of ALL remotely-stored settings in order to prevent connectivity problems from rendering the app unusable. (This opinion is based on some decades of experience in the software business, incidentally. ;-) ). Cheers, Brian
  9. FSX-MS

    > "Am I right, you are not interested in testings and reports regarding Linda 2,## with MCP1 anymore?" Good question, Roland! I sincerely hope that we are not being abandoned: should that be the case, it is something that will be felt deeply by those of us with the v1 hardware! LINDA *used* to be a community.... Easy and dismissive phrases like "...cannot be guaranteed with the MCP1 (original)..." (not to mention "...old panel...") seem to threaten that concept, which would be... unfortunate. "Our" inability to test translates to — whom, exactly? Cheers, Brian
  10. FSX-MS

    Hello, Andrew! And many thanks indeed for your prompt and informative reply — all of which is excellent news. I look forward to installing and using the new version of LINDA. ^_^ Huge thanks once again, Brian
  11. FSX-MS

    Many congratulations on the new release, gentlemen! However, before installing it I have a few more questions, if you would be so kind (the words between double quotes are taken from the pdf file in the release package): 1. "You must have also installed the VRInsight software and drivers for the Airbus FCU from http://vrinsight.com/devel_shot/ under the link 'Install Base Package VRiSim'”. Q. I don't have the Airbus FCU (only version 1 of the MCP); furthermore I have never found it necessary to install any VRinsight software with the old version of LINDA (as I explained in my 'detailed manual'). Is it really needed now? It's just that long and sometimes bitter experience has taught me not to install any software that can be done without. :wink: 2. "A new user.lua has been added...." Q. I have added a great deal of code to my existing lib-user.lua file to provide additional functions: will any of this code need to be rewritten, or are the new functions all additions? 3. The document says: "LINDA 2.5 provides full compatibility with all 3 variants of the VRInsight Combo panel" but also — "While every effort has been made to retain backward compatibility with the original MCP1 panel, there has only been limited testing and compatibility can not be guaranteed". Q. Those two statements appear to conflict with each other. Could you please be kind enough to elucidate the areas in which I might find support for the v1 MCP to be patchy? And finally.... 4. Q. I seem to recall that problems have been reported with the v1 MCP when using the PMDG 777 WIP module. Could you please confirm the status of that 777 module when using LINDA v2.5? Many thanks in advance for your reply, and for your great work in bringing the new version to us. :smile: Brian