Jump to content

funkymaggot

Members
  • Content Count

    21
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by funkymaggot

  1. Keven, Thanks, very much appreciated. Enabled and updated. Keep up the awesome work with CP!! Mick.
  2. Hi all, What is the current version that everyone is running? My CP version is currently v0.3.70 Beta, however, I read a post further down and someone has they are currently on 0.3.79 (not sure if a typo). I still get a message every time CP starts informing me that it isn't compatible with P3Dv4.2 and it is being worked on, but it has been 2 weeks now and I was wondering when this will be made compatible as I can't use zoom keys or my hatswitch properly in locked spot, which is extremely annoying. Or has there been an update released and for some reason I have an updating issue? Thanks in advance, Mick.
  3. Hi, Updated to Build 0.1.52 this evening when I started up. Loaded in an aircraft I don't have any presets for yet.... it took me nearly an hour to set up 4 camera presets. 1. Pressing any option on the side menu ie. Preset or Camera and there is a 5-10 second delay before it changes. 2. When using the Camera sliders the first couple of clicks work fine and then everything just seems to stop working or has a massive delay on it. Dragging the white dot doesn't move it and neither does clicking in the drag area. Even after multiple clicks or drags nothing happens, then all of a sudden it will work once and the movement goes on forever. 3. I bound my presets to the NumPad, as I always do, cycled through them to make sure they were OK and it was. Halfway through the flight, I dropped to the GPS preset, then when I pressed for the next view, instead of jumping to the preset, the NumPad was moving my view around on the spot ie. 8 incrementally pivoted the view up, 4 pivoted the view left and 7 diagonally pivoted the view up and left. Regards, Mick.
  4. I haven't changed anything with my FSX:SE install and have never had the boxed version installed on this system. I never used to get this issue until a recent update (today is my first update since 0.1.33). Only after update to 0.1.37 has this issue regarding the ability to find the FSX_SE.cfg started.
  5. I might just give it a go anyway... if it works then great, if not then what the hell, all I've lost is the time it takes! Thanks.
  6. It is received via a modified PS camera (that has the IR filter removed).
  7. Quick and probably really stoopid question.... I use a Trackhat Clip instead of TrackIR would this work with that? Mick.
  8. Haha... Thanks for the priority service Keven. very much appreciated. I just dropped the slider to disable it so I could get off the ground!! Will do a reboot of CP once I land.
  9. Hi guys.... Seem to have a problem that has cropped up between this mornings update to 0.1.25 to this afternoons update 0.1.27. After the update this morning everything was working fine. This afternoon after doing a few things, I came back on, CP updated and now I have the following problem: When I turn the aircraft right while taxiing, the anticipation kicks in and throws me right out the front window , through the engine cover and almost into the prop blades. When I straighten out it comes back again. If I turn to the left, I am thrown all the way to the back of the aircraft. Somehow it seems the axis of movement for anticipation has changed. No changes have been made to any of my settings etc. I literally closed it this morning and started it up this afternoon. Cheers, Mick.
  10. Assigned views to 'clear' keys on the main keyboard rather than the NumPad..... There was some improvement, however, I still sometimes had to press the keys multiple times to get them to change the view. It did seem more stable than using the NumPad though.
  11. I am using FSX:Steam Edition. Current ChasePlane as of this morning is v 0.1.22. The focal length adjustment now seems to be working OK.
  12. The biggest issue I have, even when I used to use EZDOK, is when adjusting a dial setting on the VC. For example on the PMDG 737, adjusting the BARO or Decision Height using the mouse scroll wheel and the slightest turbulence would knock you off the knob every few turns. It is great that you have thought about the pause on mouse movement, but is it possible to pause on scroll wheel movement? As this is still an issue I am having even with pause on movement enabled, because technically the mouse is stationary. Call me picky if you like but it's just a thought, if it could be added as a preference so people could enable it if the wanted to. Mick.
  13. Not sure about that... as I have nothing bound anywhere other than the NumPad. I will change some of them to main keyboard tomorrow, check it out, then let you know.
  14. I noticed this today also..... only AFTER this mornings update though, it worked fine yesterday. Mick.
  15. After double checking my NumPad in the FSX Controls settings, I can confirm that NONE of my keys are bound to ANYTHING inside the Sim.
  16. Keven, Thanks for the quick response. All of my views are set up on the NumPad, as they were with EZDok. All of these keys were wiped, as per it's instructions. I will however go back though and check them all. As for posting to let you know, you're very welcome!! Regards, Mick.
  17. Hi Guys.... I want to start by saying awesome work with this so far.... changed from EZDok the other day and this is so much better. I realise it is in Alpha and bugs/glitches are to be expected. I just want to put the issues forward that I am having as I haven't seen any posts regarding them so far (or if there are my apologies!) and if you don't know about them they won't get fixed!! 1) When changing view from Inside to Outside, using a key binding (set to the numpad), the aircraft model sometimes isn't shown and all you can see are NAV lights or strobes flashing. The view I have is high and directly behind the aircraft at a distance, to aid with taxiing. Once this has happened, if you change back to Inside view, sometimes you also get nothing there, just your scenery passing by (no panel). To reset this you need to right click on the screen, select Cockpit - Onboard (ChasePlane), and the cockpit re-appears. 2) Exact same issue as above, however, once it has moved to the outside view, some of the panels accessed using shift+1 etc, appear on the screen as well. 3) Sometimes you press the keybinding to move views and the screen judders as if it is moving but nothing happens. Quite often you need to press the bound key 3 or 4 times before it actually changes the view. 4) You press the keybinding, the screen flickers and there is a longer than expected delay before it moves. I also have the issue when using the in-game menu where you can't scroll through any of the options, however I know this one is on the list already. Keep up the great work, it'll get there eventually. Mick.
  18. That did the trick.... Thanks so much. Just have to work out how that changed. Probably one of those pesky kids of mine!!
  19. Hi, I am having a couple of issues on arriving at the TOD. I run the Descent Briefing then wait for the TOD. On arriving at the TOD I change the altitude in the MCP for the descent, then: 1) As I am reducing the altitude in the MCP (say for a descent into Newcastle, EGNT) to 2500ft. I get to around 3000ft on the adjustment and the FO says "1000 to go" then the FO makes an announcement saying "Cabin Crew prepare for landing". After we have been descending for a few minutes the FO says something about "10000" cant remember exactly what it is but FS2Crew has '10k Descent' in the procedure/checklist window. Even if I am still at FL250. 2) On actually passing 10000ft, the FO says "1000 to go". 3) Altitude callouts seem to be out of sequence for where I actually am, even though Altimeter settings are correct. Everything else checklist wise seems to work OK. I hope you can help as, although it doesn't really mess with my landings too much, it is quite annoying. Thanks in advance, Michael Barber PS. When changing the altitude at the TOD, I have also tried changing it up to 5 minutes prior to reaching TOD and also by asking the FO to adjust it. This brings about the same result.
×
×
  • Create New...