Gumps

Hi Phil That graphic and the text below it in your post don't go together. The text goes with the graphic below it in the original posting (not shown in your excerpt). With the graphic shown, a person would click on the drop down arrow, and select their controller. What happens when you open that 'combo box' - your controller is not shown? Once EZdok recognizes the controller, you can assign individual buttons to camera views. I don't believe the location of the CH Manager has any bearing on this. You're welcome to PM me; perhaps we can figure out another way to attack this.

Hi Phil Since I already have a saved profile for the NGX, I click the 'open' button (folder icon) and select that map. In order to assign a DirectX function to a particlar button, in this case the red button with the arrow pointing to it...push that button. That way CH Manager knows which item you want to edit. With the "DX Mode" check box checked... Select the "DirectX Device" - in this case "CM Device 1"... Then select the DirectX Control - in this case, "Button 2". In EZdok, you have to enable the controller or joystick. Then, with the view you want to assign a button to highlighted on the left,click in the Joystick field in the upper right, and push the desire button. Note that I also have the key command "N" assigned to the same view. My Logitechgaming mouse has the letter "N" assigned to one of its buttons. I mentioned previously'sharing' several views between my joysticks and the mouse for convenience. I had to play with EZdok and CH Manager a while before I got used to them. Hope this helps.

Hi Phil - I'm at work at the moment but I'll take some screenshots later and post them. Cheers

Hi Phil I unchecked the "Use as POV" in CH Manager for my hatswitch. Instead, for each of the four directions (there are actually eight), I assigned Direct X 'controls'. For example, Up = DirectX Device 1, DirectX Control 1, Right = DirectX Device 1, Direct Control 2, and so on. It makes a lot more sense when looking at Control Manager. In EZdok, I select the particular camera view I'm interested in, and then assign the CH controller button, or in this case, POV button. I don't use a POV hat at all in FSX to look around, since I have TIR and also use the mouse for outside views with EZdok. If you don't already have it, there's a guide you can download here. It's from the CH website, and it's one of those 'dummies' guides. No insult intended, heck, it's more advanced in places than I need. I don't do fancy scripting with CH Manager, I just have various profiles setup with desired key commands. Once setup, you start CH Manager before a flight, download the profile into the controllers, and close CH Manager.

Hi Phil I have four CH controllers hooked up - FlightStick, Pro Throttle & Pedals, and Throttle Quadrant. I have most of the viewing controls setup on the FlightStick - the hat switch and others. There's a singular red button on top that I use for my main panel view, since it's easy to remember when I just want to see the centered view. I also have some viewing controls on the Pro Throttle, which isn't used (on this aircraft) as a throttle at all - I just use the buttons. I can reach over and grasp the throttle and find the buttons I need without having to look. These are functions I don't need access to regularly, but more occasionally...like some of the EZdok outside view cameras. I also use a Logitech G700 gaming mouse. Since I fly the NGX in VC, I have to use the mouse a lot more than I used to. (I have multiple monitors and touchscreens for other aircraft.) I fly right handed, with the stick, and I use the mouse with my right hand. By programming the main EZdok viewing commands on the gaming mouse, I can 'move' around the main views - Main Panel/Overhead/Control Stand - without taking my hand off the mouse. I've also assigned the TrackIR Center and On/Off controls on the mouse, which aids in manipulating the aircraft. Overall, I find operating the aircraft cumbersome in VC (versus 2D panels and touchscreens), but with the combination of EZdok, TIR, and my CH controllers has surely helped greatly. I still do use touchscreens for the CDU's and MCP. Rambling a bit here, but perhaps it is of interest to someone else.

Hi Phil Not sure why you encountered the behavior you cited regarding EZdok and CH Manager, but I can confirm I am using both together without issues. I have various EZdok 'cameras' assigned to two of my CH Controllers. I will say it took some time for me to get the hang of both EZdok and CH Manager.

Ran You can assign keystroke commands to your CH Yoke buttons using CH Manager - the applet provided by CH Products. You may want to download the latest version. I have several CH controllers and use various keyboard macros via CH Manager. I have also gone into FSX 'Controls' and deleted most of the default key commands - ones that I don't use - so that they are available for my use (to avoid conflicts). I have various 'profiles' created in CH Manager for my different addons. It's actually a fairly powerful utility. Good luck.

To bring this saga to a close, Hotfix 4 cured the stutter/hiccup issue I've had with the NGX. I don't know what you folks did, but thank you PMDG for fixing this!

Hi Brad I'm guessing you're referring to my earlier post in this thread... ====================================In Full Screen Mode, unlike any other FSX addon I've used, the sound changes when the emphasis is put on the touch screen, like when I input data in the CDU. I have to click the mouse on the main screen to reinstate the sound...it's like it's slightly muted, very noticeable...and odd.In Windowed Mode, this change in sound does not occur.==================================== That's interesting that FSUIPC was revised to address this. I'll have to download the latest version. Thanks. Also, if I'm not mistaken, Hotfix 3 addressed this issue for the NGX.

Noel I just returned from a month of vacation. During my time away, I made a list of additional items to test upon my return. Unfortunately, nothing I've tried will stop these hard stutters. For clarification, I'm referring to 3 to 5 jarring stutters experienced during a takeoff, crosswind, downwind, final and landing - closed circuit flight. Last night, I turned all of the sliders to the left...and it still does it. With FSX at its most basic, with no traffic, no EZdok, REX textures removed...I still get these hard stutters running at 4.8 Ghz. (I have run at stock speeds and tried many other tweaks and adjustments, all of which are listed in earlier posts in this thread.) Hi Ryan Thank you for your thoughts on this. 1. Yes, I have tried all manner of Nvidia Inspector settings, including just off. 2. I don't have any antivirus on my machine - it's just used for FSX and I do my internet stuff on other computers, including downloads for FSX. 3. I'm glad you mentioned all of this regarding trying to use Process Monitor. It's next to impossible to nail down what's going on, and it sounds like from your informed view, any manner of red herrings are around to tempt one off onto some bunny trail. I've spent time trying to trap things with PM - sounds like it's a lost cause. And I keep running into Peter Cottontail. (For those old enough to remember - "Here comes Peter Cottontail, hopping down the bunny trail, hippity hoppity...." -- Yes, I think I'm starting to go over the edge on this one!) Ryan - One thing I'm always suspicious of, is the sound system. I've had stutters coincide with sound events, but not always. Early on, I disabled my Gigabyte onboard sound, and installed an Asus sound card, with no effect. I've turned the sound off in FSX, but have wondered if the *.wav file is still executed, but just muted. It may be nothing, but I've noticed that sometimes it's a sound event that seems to trigger the stutter. Do you have any thoughts on that? Here are some of the items, in addition to those listed earlier in this thread that I've messed with: - Downloaded and installed the latest NGX RTM, which I think has Hotfix 3...I couldn't find the standalone Hotfix 3 file. - Tried various FPS limits from 20 to 60, with and without the Frame Rate Limiter, Windowed and Full Screen. - I've loaded (clean install) at least half a dozen different Nvidia drivers, from the 260's to the latest beta. - Tried VSync on/off, using Nvidia Inspector, or FSX.cfg. - Assigned EZdok to Core 0...tried it without EZdock. - Adjusted Max Prerendered Frames settings in Antilag Frame Rate Limiter and Nvidia Inspector. - Eliminated the fx_skidmark.fx file. - Removed my CH Controllers and installed on different MB USB ports versus USB hub. Perhaps it's some bad combination of the NGX and my particular hardware setup. This surely does not happen with other complex addons on my machine, but the NGX appears to be unique among all addons, raising the bar to new levels. I had mentioned in an earlier post, that I had installed the NGX on another HDD with a different OS and FSX installation (Vista64), but on the same hardware, with no luck. This morning I plan on installing the NGX on my old C2D system (3.8Ghz / GTX560TI) and see what I get. That machine has FSX + SP2, versus my current SB machine with FSX Gold/Acceleration. We'll see what happens.

I've noticed the same behavior on the NGX (only)...when in Full Screen Mode - seems OK in Windowed Mode. Odd.

Milo I just read that post, and was thinking the same thing. I'll be interested to see where that investigation leads. I hope PMDG is active on the matter. FYI...I managed to try a few other things. I installed Nvidia's 280.xx drivers (again) but this time was careful to load only the video driver, rather than accept the 3D Vision and HD Audio drivers too. I saw calls to 3D Vision when using Process Monitor. It's probably the placebo effect, but it seemed to help some. For a test, I also installed a Vista 64 HDD that I had FSX on, and had used when I first built this SB machine. I installed the NGX on that disk, same machine, but different environment, and the problem persisted. I also took out the GTX580's and installed a GTX560TI from another machine, just to eliminate one more thing. I hope someone figures this out.

Noel Yes, that's correct. For me, this is unique to the NGX, though I wonder if an issue has been masked perhaps, because other addons don't have so much going on. My FPS are fine, and it is normally very smooth aside from this jarring stutter. I used Process Monitor today for a while, trying to trap the offending events. Interestingly enough, "FNPLicensingService.ext" caused a stutter. In researching it on the web, it was tied to Adobe for (as I recall) authentication. Well, I figured I didn't need that. Wrong. When I renamed that and it's cousin in the folder, fnp_registrations.xml, the NGX said I needed to activate when I tried to load it on the next session. I noticed PMDG referenced in the *.xml...guess it needs to be there. If it's an activation check, I wish it wouldn't happen in flight. So, I couldn't test with this out of the way, though it's not the only process I think that has interfered. I found UT2 loading traffic, and have since been flying with that off. Still getting the odd hiccup. I also caught MSI Afterburner horning in on the party. I turned off the monitoring and manually set the fan speed to a safe value to test. For a change I tried a complete flight from Helena, MT to Missoula....probably saw 15 or so hiccups. Enough to kind of spoil the atmosphere. I'm in the midst of packing for an overseas trip, so I've run out of testing time. Robin Thanks for your input. A number of those items were addressed earlier in the thread, and no I don't have HT on. I know it's getting to be a long thread. Thanks for your input, and you're right in suggesting taking things back to basics and eliminating things. That's really what I've been doing, rolling things out of the mix and testing for effect, trying to eliminate things. It acts like a momentary intrusion. It a bit of a mystery, this one. All the best

"Sorry to be blunt, but you don't understand the first thing about how your computer actually runs software, or anything about bus architecture. If you did, you'd know that there are multiple items that could cause the system to momentarily freeze, or that 80% of the hardware you just listed has nothing to do with it." Best regards,Robin. =========================================== Hi Robin I was just trying to make the point that I'm surprised at seeing a performance issue with a higher end system. Surely one's hardware, including the CPU, GPU and HDD's play a role in the performance. Not that it can't happen with such hardware, of course...my guess is that it is a software issue. The NGX is the only addon exhibiting this behavior. It sounds like you're well versed in these matters. Do you have any suggestions (beyond those I've listed previously in this thread)? I would appreciate any insight you might have. Thank you

Hi Vic Thanks for weighing in. I will say, I've triple checked that the AutoSave feature in FSUIPC is not checked. I've been through every tab in the app, making sure the weather features are not enable, etc. Also, I'd have thought I would have seen this interference in Performance Monitor. (Discussed earlier in this thread.) It seems that something else is going on...come gremlin somewhere. Cheers,