Mustang-242

Members
  • Content count

    31
  • Joined

  • Last visited

Community Reputation

7 Neutral

About Mustang-242

  • Rank
    Member

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No

Profile Information

  • Gender
    Male
  • Location
    East Midlands, UK
  1. Indeed it's not the end of the world that ChasePlane is unavailable. I could still fly. But the fact TrackIR is also not working, which I can only assume is related, is a big problem. The pan-rate in FSX with my yoke's hat switch is painfully slow, even with the button repeat rate on max. A huge hinderance when flying a GA aircraft. I have previously disabled mouselook (space bar) in FSX's own bindings, to avoid conflicts with CP's mouselook, and I can't easily remap it because it's not called anything obvious in the FSX key bindings menu! So, yes, I could find a workaround for everything but it will take quite some time to faff around in .cfg files to make lots of adjustments, just to get some basic ability to look around quickly and easily. If TrackIR was still functioning then I would be quite happy without CP, but for whatever reason, TrackIR doesn't even know FSX-SE is running. I cannot be sure that CP is to blame for this but I am very suspicious, as I have not have problems with TIR & FSX before... Having been on the receiving end of technical support for many years, I am very patient with IT problems. Losing nearly all control of my views, both from CP and TrackIR, really is a big problem for me. All we can do is to be patient, I know the developers will work hard to solve this. They have demonstrated their dedication plenty since CP launched and for that I must congratulate them. Now they need to find a suitable compromise between online sync services, anti-piracy measures, and customer needs. I wish them luck! Martyn
  2. Agreed, needs to be able to run offline even if it comes with a warning that any changes to cameras will not be saved, for example. I was left scratching my head this morning as I'm about to embark on another leg of my around the world trip, but ChasePlane refuses to work. Quick trip to the forums and I find the reason in this thread. Not good! It's probably the only bad thing I've found with CP so far, but it is quite a big one. Edit: To make matters worse, even TrackIR is not working in FSX now... not sure if that is the result of CP being offline due to the new TIR integration. So indeed it looks like I am grounded for now Martyn
  3. I have half functionality with the OC and the J41, after a completely fresh install of Windows 10 and FSX-SE. (I also have the 737NGX though) I can install J41 liveries via the OC, but I can't configure the aircraft options - the page options but no changes are saved. To edit the aircraft options, I found that running the "PMDG BAe JS4100 Configuration Manager" from the Start Menu works just fine. Maybe it will work for you too if you have the shortcut available.
  4. Really looking forward to 1.5, keep up the great work! I've recently reinstalled Windows and FSX on an SSD. The installation of ChasePlane was so simple compared to everything else. The cloud-based saving of presets & options is such a breath of fresh air compared to all the other stuff I've had to migrate from my old install, like aircraft engine hours, liveries, configurations and scenery etc. Thanks Keven & team! And happy holidays!
  5. FSX-MS

    OK, that explains the OC behaviour at least, thanks Kyle. I knew the J41 wasn't officially supported (forgot to mention it) but many have had luck getting it to work. I have it working now after two steps: Running the SimConnect.msi for version 61355 from the SP1 folder (FSX root\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-SP1) - after this the activation window appeared when I selected the J41 from the Free Flight menu. Manually installing the glassga.ttf font into C:\Windows\Fonts from my old Windows install - I moved to a new SSD so still have my old installation available on the old drive. This was mentioned in another thread here, to get the FMC to display any text. The J41 configurator tool doesn't work via the OC (settings are never updated to the .ini file in the FSX\PMDG directory) but the dedicated link in the Start Menu still works just fine for setting the aircraft's options. After all that, I still had an issue (which I occasionally saw in boxed FSX) with half of the screen covered by a flickering white texture whilst in the virtual cockpit, but I understand that's due to the icing effects. Having turned them off via the J41 Configuration tool all seems to be fine. Time will tell when I try to fly it! I understand that IAS hold won't function in FSX-SE but I can live without that.
  6. FSX-MS

    I've a problem of a similar but different nature. I'm on a new Windows 10 install, fresh install of FSX-SE. I've added the 737NGX and got the latest Operations Centre, now I've installed the J41, getting the latest installer via the Aerosoft support site. Having installed it, the Operations Centre sees it (as the J41 FSX-SE version), but the aircraft is inoperable - I've not had any activation dialog appear yet... which probably explains why. When I re-open the OC and go to the J41 settings page, no options are ticked at all and the refresh rates of the displays are all set to zero. I'll remove and re-install it tomorrow. Besides changing the default flight to one with the MS Cessna 172 on the ground which has the engine shut down, avionics and battery turned off, it's pretty much a clean install at the moment. I can use Ctrl+E to get the J41 started but it doesn't trigger anything. Also tried swapping aircraft in-game rather than from the menu. Will report back if I figure it out.
  7. When I reported a minor bug to their support team recently, the response indicated that it was unlikely to be fixed as the J41 isn't likely to get any more updates which is hardly a big surprise. However, I wouldn't consider that an absolute and final answer on the topic, just the opinion of the agent, so let's hope it gets a refresh eventually. It fills a nice spot in the fleet and the two-tone cockpit is a lovely office to sit in! :smile:
  8. For me it was the DreamFleet Piper Archer II for FS2002. I actually went halves on it with a friend, as the idea of buying a single aircraft which was nearly as much as the game/sim itself was quite a new concept at the time, and that lessened the financial blow. Nowadays, the base sim is often at the cheaper end of the scale compared to some of the add-ons I've bought! Times sure change. Back then a VC was a barely-usable novelty, though I always found it far easier to land in that view, even if the instruments were barely legible.
  9. Easiest short-term fix would be to have ChasePlane recognise the A2A aircraft which include vibration effects already and not use its own effect it during shutdown on those aircraft. I also noticed it yesterday on the A2A Comanche as well. The camera movement came a couple of seconds after the prop stopped. I quite liked the CP camera 'wobble' though; it was a little more significant and felt more realistic than the small panel vibrations of the A2A effect, so hopefully in the long-term it can be worked out and left in.
  10. As always, thanks for the reply Keven and for adding that one to the list. Do remember to take an occasional well-earned rest though!
  11. I use TrackIR in combination with ChasePlane by simply using the same key to enable/disable each application. They stay 'in sync' (only one enabled at a time) as long as I remain in the cockpit (on-board CP view). I sometimes like to use the spot view in combination with TrackIR to quickly look outside and pan the camera around the aircraft. However, when I switch to another view by some means, then switch back to the cockpit (on-board CP view), the "Global Enable" setting is automatically switched back on. At this point, both TrackIR & ChasePlane are fighting for camera control, so I have to open CP or the in-sim menu and disable it again. I can't really think of a particularly useful reason for this behaviour being programmed in. Assuming there isn't one ( ), could it be prevented in a future update please? I know there's a fuller integration for TrackIR available with other software as in the pinned threads, but like some others I'm holding out for the proper integration. Thanks, Martyn
  12. Thanks Keven for the quick fix! Your latest updated indeed fixed it. Glad to have found a minor bug, whatever it was, as I thought it was something I had done. Regards, Martyn
  13. Thanks Keven. I am indeed in the Outside (ChasePlane) view but the CP zoom keys haven't worked on external views for quite some time now. Only the first couple of versions I used had working zoom in external view. Same for all aircraft. Works just fine on the internal view though. Odd! Maybe a complete clean reinstall is in order. I haven't changed much with my installation but it's likely something small has caused it. Here's a report from your new report function, with e-mail address removed for obvious reasons ---------------------------------------------------------------------------------------------------------- --------------- ChasePlane Report by x on 11/22/2016 11:38:01 PM UTC --------------- ---------------------------------------------------------------------------------------------------------- Version: 0.1.75 PLV: 0.1.68 OS: Microsoft Windows 10 Home .NET: 4.6 RC or later Running Sim: FSX 10.0.61637.0 Supported Current aircraft: A2A Piper PA24 250 Comanche Current aircraft cfg: D:\Microsoft Flight Simulator X\SimObjects\Airplanes\A2A_Piper_PA24_250_Comanche\aircraft.cfg ---------------------------------------------------- --------------- Installed Simulators --------------- ---------------------------------------------------- FSX "D:\Microsoft Flight Simulator X\" ------------------------------------------- --------------- Preferences --------------- ------------------------------------------- experimental_version = False freq_ref = 120 ctrl_freq = 60 freq_trim_ms = 1 ui_refresh_ms = 500 ui_anim_duration = 0.4 view_sel_anim_in_ms = 0.2 view_sel_anim_out_ms = 0.1 view_sel_delay = 250 mouse_middle_view_switcher = True turb_pause_ms = 1 always_on_top = False debug_show = False vas_show = True vas_warning = True vas_remaining = False vas_warning_treshold = 400 turb_wind_amplitude = 1 startup_glob_enable = True app_auto_launch = True mouse_middle_cam_look = True pause_turbs_on_mousemove = False doors_enabled = False mode_cinematic_duration = 30 mode_cinematic_delay = 10 mode_cinematic_vas_protection = True focal_offset = 0 preset_transition_time = 500 boostFactor = 5 cam_speed_multiplier = 1 gyroscopic_speed_multiplier = 1 cam_turb_factor = 5 joystick_default_dead_zone = 100 user_statistics = True auto_cpu_afinity = True cpu_afinity = 0 show_whats_new = True disable_advanced = False data_overlay = False ------------------------------------------------------------- --------------- Aircraft's Camera Definitions --------------- ------------------------------------------------------------- CFG created on 10/4/2015 1:00:20 PM UTC CFG modified on 11/17/2016 11:16:46 PM UTC [CameraDefinition.0] Title = "Right Flap" // (Disabled by ChasePlane)HotKeySelect = 4 [CameraDefinition.1] Title = "Right Aileron" [CameraDefinition.2] Title = "Right Wing Tip" [CameraDefinition.3] Title = "Right landing light" [CameraDefinition.4] Title = "Right Main Tire and tie down" [CameraDefinition.5] Title = "Right Fuel Tank Level [CameraDefinition.6] Title = "Fuel strainer and front tire" [CameraDefinition.7] Title = "Propeller Check" [CameraDefinition.8] Title = "Engine inlets and air filter" [CameraDefinition.9] Title = "Check engine oil" [CameraDefinition.10] Title = "Left Fuel Tank Level [CameraDefinition.11] Title = "Left Main Tire and Tie down" [CameraDefinition.12] Title = "Stall warning, and Pitot tube" [CameraDefinition.13] Title = "Left landing light" [CameraDefinition.14] Title = "Left Wing Tip" [CameraDefinition.15] Title = "Left Aileron" [CameraDefinition.16] Title = "Left Flap" [CameraDefinition.17] Title = "Static vent" [CameraDefinition.18] Title = "Tail" [CameraDefinition.19] Title = "Verify Baggage Door is Locked" [CameraDefinition.001] Title = "Instruments close / IFR" [CameraDefinition.002] Title = "Avionics and engine" [CameraDefinition.003] Title = "Right Seat" -------------------------------------------------------- --------------- Cameras.cfg file for FSX --------------- -------------------------------------------------------- CFG created on 3/9/2012 11:32:52 PM UTC CFG modified on 11/20/2016 10:23:09 PM UTC [CameraDefinition.012] Title=On-Board(ChasePlane) HotKeySelect=1 [CameraDefinition.013] Title=Outside(ChasePlane) HotKeySelect=4 [CameraDefinition.014] Title=Static(ChasePlane) HotKeySelect=5 [CameraDefinition.001] Title=Cockpit HotKeySelect=2 //[CameraDefinition.002] //Title=VirtualCockpit //HotKeySelect=1 [CameraDefinition.003] Title=Spot [CameraDefinition.004] Title=LockedSpot HotKeySelect=3 [CameraDefinition.005] Title=FlyBy [CameraDefinition.006] Title=Top-Down //HotKeySelect=4 [CameraDefinition.007] Title=NearestTower NoSortTitle=True [CameraDefinition.008] Title=FacilitiesTower [CameraDefinition.009] Title=FacilitiesRunway [CameraDefinition.010] Title=AIPlanes [CameraDefinition.011] Title=MultiplayerPlanes --------------------------------------------- --------------- END OF REPORT --------------- ---------------------------------------------
  14. I'm not sure if I'm the only one with this issue as I haven't seen any similar posts (but may have missed one, apologies if so). For the last week or so (through several updates), my mapped zoom buttons function perfectly on the internal CP view but don't work at all on the external CP view. All my other camera keys/axes work fine for both internal & external. The buttons I'm using for zoom are the top shoulder buttons on my PS3 controller, seen by Windows as an Xbox 360 controller. Anybody have an idea why they only work on the internal view? I have a pair of buttons on my yoke set up with FSX's own zoom in/out commands. These work in the external view on the CP camera (suggesting CP is not controlling the zoom), as do the +/- keys on the keyboard, so I'm not completely stuck. In the internal CP view, where the CP-mapped keys do work, I cannot use the FSX zoom keys to change the zoom, as the zoom is overridden by CP's camera control. If I try to use them, I only see a momentary change in zoom level before the camera is reset, which is expected behaviour). Besides this issue, CP is running very well for an alpha. I do see occasional glitches with switching between inside/outside views but recent updates are improving that. The new announcement for alpha 2 sounds fantastic. Keep up the great work! Regards, Martyn
  15. At the moment you can't (as far as I know), but hopefully in future it will be a toggle option. I'd like to see it too. You can only 'roll' the camera to make it level with the horizon, but any rotation (panning) will make it skewed again. Alternatively, it may just be that the ChasePlane controls can be used to manipulate the default "locked spot" view in future, which would more or less give the same result we are looking for. Whether locked spot allows the camera to be rotated away from pointing at the aircraft's centre/origin, I do not know. Probably not knowing FSX... DCS and Rise of Flight have excellent external cameras where you can freely orbit around the aircraft, but toggle a kind of 'dolly' mode where the camera can rotate without moving. You can set the aircraft nicely off-centre, then switch back to orbit mode and have the aircraft stay off-centre as you rotate the view. Great for screenshots. I often find orbit cameras faster & more convenient than a truly 'free' camera, such as CP uses for externals at the moment. But that too has its uses of course! Fingers crossed for the future development of CP