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,

I've spent quite a few hours on trying to solve this, but no real luck so far. I have... ...tried several Nvidia drivers, including 270.xx and the latest 280.xx. ...I put my two GTX580's in SLI for laughs. ...used various Nvidia Inspector settings. ...tried 1680x1050 resolution on my 30" monitor (yuck!). ...installed the PMDG Hotfix. ...removed one DDR DIMM, leaving one 4GB. I messed with the timings and speed. I will say, this had a significant impact on performance, all bad unfortunately. Turns out all was good with the original settings I settled on when setting up the system. This Mushkin Redline is rated at 1600, which is where I'm running it. Makes me want faster RAM though. ...replaced the NGX Trim *.wav file with a blank one, since I've seen the hiccup while trimming and coincidental with other sounds. BTW, I've used this to replace other annoying *.wav files that I got tired of listening to on other airplanes..."Don't sink", "Caution Terrain" etc. Hey, it's my business if I want to hit the terrain! ...and yes, I even tried loading the 747X first. Whew, talk about a primitive looking VC...in comparison to the NGX, that is. Noel - I experimented with creating some of those missing files in the .../Bucket/ folder, like the soundAI.CFG. I figured if the program was looking for a file, well then I'd give it one! It worked for one or two, but the *.CAB files didn't work out. Besides, when using PM, I notice a big stutter when a bunch of Orbx textures were loading. I'm a bit hampered when using PM since it kills EZdok and TIR. I've noticed that if I don't look around with TIR, but rather leave it paused, I get less hiccups. FWIW, one of the places I've been testing is Helena, Montana (KHLN) which has Orbx scenery. I've just done closed circuit work. Sometimes it's only 1 or 2 stutters in the course of a takeoff and landing. Other times it's 6 or so. If they were the "microstutter" variety, I wouldn't be so concerned. But these are sudden stoppage, really jerky, At this point, I've run out of ideas. Perhaps PMDG can sort it out. I'll be leaving for a month of vacation in a couple of days. Hopefully my computer will heal while I'm gone. Cheers,

Hmmm, that's interesting. Please do let us know how you make out on that.I'm also optimistic that PMDG may be able to get to the bottom of this. I'll bet they know more about FSX than anyone. In the meantime, this is forcing me to turn over every rock, and in the end, I may end up with better performance as a result. Thanks for your continued involvement in this.All the best,

Hi Tim, You're right, I didn't include the things that were basic. Heck, it would be too long a post! I figured the reference to NickN's hallowed guide would suffice. (Talk about a long post!) You may not have noticed in one of my subsequent posts that I indeed tried the system at stock clock, and that didn't help. Thanks for the thought just the same; sometimes we overlook the easy things. It can just be something little. My RAM is not overclocked, but rather is at stock speed. I've stress tested the memory as part of the system overclocking process. But, I've not tried removing one stick. I have observed the memory useage as part of the troubleshooting and can see that I should easily be able to get by on 4G...so I'll try that tonight. Thanks for that suggestion! Your comments are very much appreciated. Cheers,

Noel and hammish777,I installed the Process Monitor (PM) and noticed the same items in your screen capture Noel. I set the PM to filter just the D:\Microsoft Flight Simulator X\ directory first, and later whittled it down to just the D:\Microsoft Flight Simulator X\...Bucket\ directory. Those unsuccessful process calls appear during the stutter, but also seem to appear at other times not associated with the stutter. (??)Something else I noticed. When I start PM, it causes EZdok to crash. When that happens, I can't use TIR or the various EZdok cockpit views. I tested with it anyway. PM sure has an effect on FPS, but by itself, doesn't cause the hard stutter. I will say, looking around with TIR naturally causes the view to change rapidly which would seem to 'stress' the graphics more than a static view. The airplane itself doesn't turn that fast. Kind of like the stutters folks can get when turning the airplane while taxiing on the ground. That is the time when the outside view changes the quickest.The other thing I noticed, was that more than once I got the stutter when using elevator trim. May have been coincidental, but I've seen this all along sporadically. I didn't capture that with PM.And by the way, I was flying with one finger on the Pause button, to and capture the stutter. Or really, to shorten the list the PM is putting out. Too bad we don't have an Event Trigger. Maybe PM has one, but I couldn't find it.It's odd that FSX is looking for file names that don't exist. What's up with that? Odd. Wish I knew where to turn that off.I've not heard back from PMDG yet.Cheers,

Noel - I have not gotten a reply back from PMDG, and suspect that they're are busy stamping out fires...very understandable. Still, since they built the NGX, surely they will have some insight into this since it's unique to this addon. At least it is for me, and I have all of their FSX addons, plus others. I read with great interest your investigation with Process Monitor. I'll try to follow suit...just got home from work and will go upstairs and start poking around. I'll report back what I find out. Lain - I've not had any luck with the 2 FPS limiters though I was primarily looking at things in Full Screen Mode. I might take another swing at this, but based upon Noel's observations, I suspect the solution is somewhere else. Thank for bringing this up though. Fritz - I don't have antivirus software installed, since mine is a dedicated FSX machine. Good to know you cured your ills though. Might help someone else. McDaniel - It can happen at any phase of flight, and on the ground. And yes, it happens at default FSX airports. As an editorial comment....this addon is so worth tracking this down and eliminating it. Heck, the FPS are great! How did PMDG pull that off? If the FPS were low, there would be no hope. IMO, this is surely the gold standard for flight simulation. It's every bit as good as I hoped it would be, and well worth the wait. Remember all of the whining over release dates and such? Isn't it nice to read the forum without all of that? More later. All the best,

ZachI did try the antilag FPS limiter, but I didn't notice any difference. The RenderAheadLimit was set at "0". But, I was using it in Full Screen Mode (and also experiencing the Black Screen thing). Lately, I've been experimenting with Windowed Mode, so I'll try the antilag tool again.Richard, I was having the issue prior to going to 275.33, but if you're saying this version caused you grief, perhaps I'll revert back down.Oddly enough, sometimes it's smooth sailing for quite some time. This is aggravating.hammish777 - Thanks for the link to the process monitor. I downloade it and I'll install it later...I was looking for something like this. Much appreciated; I'll share what I find out. Hopefully it's not too hard to use and I can recover something meaningful.Cheers

================================Does it look like this? ================================ Wesley, indeed it does. My FPS are smoother (maybe FRAPS is causing a hit in the video), and the hiccup is a bit shorter, but yes, that's what it's doing. Mike - Thanks for replying, and I see we have similar specs and you are not having the issue. That means there has to be a solution...a software or hardware change - but it's not normal. Again, thanks for confirming this. BTW, no anti-virus software involved though I appreciate the suggestion. This machine is only used for FSX. OK, and Crysis on occasion. For anyone following this thread, last night I tried the following: I ran my machine at stock i7-2600K speeds. No help. Sometimes several minutes will go by before I see a hiccup. Sometimes 30 seconds, sometimes 7. It's all over the place. I messed around with running in Windowed Mode, and that seemed to help. It could be wishful thinking, I'll test more later tonight. I also noticed a different behavior in Windowed Mode vs. Full Screen having to do with the sound and multi monitors. I like to run a 17" touch screen on the side for the CDU when using VC/TIR on my 30" monitor. 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. I prefer Full Screen, but am finding with the NGX I may have to stay with Windowed Mode. I spent a bunch of time dorking with the Title Bar and Border colors, trying to tone them down so they were not so distracting. Also, I notice a drop in FPS from 38 to 22 when going to Windowed Mode and stretching the Window to fit my 30" monitor. However, when I used the Maximize button, the FPS seemed to be the same as Full Screen Mode, though I understand the Alt + Enter Full Screen Mode to be a different animal. I did watch the CPU, GPU, and Memory loading while running in Windowed Mode. Not surprisingly, all four cores were often maxed out. (I tried Affinity Mask 12, 14, 15 and None during the course of events.) The GPU didn't seem to make it over 60%; the main system memory (8Gb) usage was quite low. Still trying to find the root cause...and the cure. Cheers

Hi I've tried the NGX on my 7 screen setup - TH2go for 3 view screens, DH2go for main instrument panel across 2 touch screens, a side touch screen for CDU and aft pedestal, and the last screen above for the overhead. This is how I planned to fly the NGX, but I've been disappointed with the quality of the 2D panels, the lack of a 2D throttle quadrant, and no F.O. DU's. Instead I'm using a 30" monitor with one of the touch screens to put the CDU on, for VC with TIR. I know a lot of folks don't understand why anyone would want to use 2D panels, but for multiple monitors, it makes a lot of sense. Having said that, the VC in the NGX is so spectacular and clear, that I'm enjoying flying it that way more than any other addon. And, the HGS helps get around the conundrum of not having enough vertical pixels to see the instruments and the runway on approach. You don't need to see no stinking instruments (although you still can) with the info displayed in the HGS. Brilliant PMDG!

Trisager - Thanks for that suggestion. I have tried locking at 30 FPS with the same result. It just doesn't appear to be FPS related, since I'll see FPS around 40, and then *hiccup* (good term by the way ilias). Mark - OK, so maybe I'm not the only one.ilias - Looks like you too have a higher end system and are seeing the same thing. I submitted a ticket to PMDG though I'd expect it to be prioritized lower than those that can't get activated etc. One thing I have not done is to try and monitor the GPU and CPU while flying to try to get an idea where the saturation might be occuring.Thank you all for taking the time to comment.

Good FPS…but Plagued with Momentary Freeze First off, kudos to PMDG's team for putting out such a complete and realistic simulation. This is not a complaint post…rather, I really want to try to get to the bottom of an issue that's tarnishing my experience with this spectacular addon. I would think the overhead of all of this wizardry would take a toll on frame rates. Surprisingly, the performance is very good. My FPS are in the mid-30's most of the time (locked at 40). But I get a hard stutter sporadically - not microstutters plural, but just a momentary freeze of the video. It's very jarring. It can happen at rotation, or when looking around with TIR. It's the only addon with this behavior, and I only fly complex addons. I've seen the stutter come and go, sometimes 7 seconds apart, or maybe 30+ seconds, or no particular timing. In some cases, I've seen the mouse cursor or was it the Win7 'busy' icon, flicker on the screen. It's as if somehow the system becomes saturated and has to catch up. I see this just flying VFR with no FMS activity and weather set to 'Clear', flying in non-Orbx, generic FSX scenery. This doesn't sound like the 'freezing' issue others are reporting, the sim doesn't stop responding, it's just a momentary heavy stutter. I'm somewhat surprise, because my system employs an OC SB (4.8) with dual SATA III SSD's and two GTX580's. Is anyone else seeing this as well? So many have reported such sterling performance, I'm thinking my issue is peculiar to my setup. I'd like to know if others are seeing this, and if anyone has an idea that might solve this. System specs are in my signature below. The system was set up using NickN's guide in addition to tweaks I've become familiar with over the years. Addons include REX2, UT2, EZdok, TIR, FSUIPC, and Orbx scenery. I don't use an external wx engine. I've used Bojote's FSX.cfg tweaker. First off, I switch between using multiple monitors, and a 30" Dell with TIR. I whittled things down by disconnecting all monitors except the Dell, and removed the second video card. I do note that in either configuration, it's a fairly high resolution - 2560x1600 for the Dell, 3840x1024 for multi monitors (with additional screens as well). Here's what I've done to try to solve this (all with no help): -- I followed the items in the NGX Introduction. -- I've tried 2D panels versus VC. -- With only one video card and monitor, I've tried the FrameRate Limiter app (which I've never been able to get to work with multiple monitors/video cards). -- Without the Frame Rate Limiter, I've tried locked at 30 FPS, my usual locked at 40, and Unlimited. -- I delved into every tweak I can think of: Bufferpools, TBM, AffinityMask etc. -- I've turned off Autogen. -- Disabled UT2. -- Turned of the F.O.'s DU's. -- Made sure FSUIPC Autosave is not checked. -- Tried GameBooster. -- Windowed Mode versus Full Screen Mode. -- Updated my Nvidia drivers to 275.33. Reset Nvidia Inspector (per Ryan's instructions). -- I've had problems with sound before, and I started to think it sometimes froze when a *.wav file played. So disabled the Gigabyte/Realtek onboard sound, and installed an Asus mid-range sound card. -- Disabled TIR. -- Disabled EZdok. In summary, for the life of me, I can't seem to pinpoint what is causing this stutter. As I said, it doesn't sound like it's related to the freezing issue others are having. (??) I will say I have seen some occasions where the keyboard inputs have no effect when trying to assign keyboard definitions in the CDU. This is the only addon that does this, but it may be that it's just surfacing a shortcoming in my software/hardware setup. I just can't figure out what it might be. If anyone has a suggestion, I'd sure appreciate hearing it. I'll put this in as a ticket to PMDG, but I would like to know if anyone else with a similar system is seeing this. I know some folks would just pass it off as something momentary, and perhaps pay it no mind. For me, it's jarring and greatly disrupts the simulation. Again, this is not a microstutter, this is a full stop of the video for part of a second. Thanks.