ilellis

Thanks Pete, I'll check that out! Just point me in the right direction... Iven

Howdy Pete, I recently purchased a new nVidia video card (changing over from an ATI video card) and after doing so run into a new and unique problem. While moving my mouse cursor around in the 2D cockpit and putting the mouse on various hotspots (such as the cockpit gauges or buttons) and even the maximize and minimize buttons at the top right corner of the screen (all of which display labels such as the in-cockpit popup labels) that the cockpit 2D rendering would disappear from the mouse cursor to the bottom of the screen leaving only the "outside" scenery. Depending on what I pointed at such as the minimize button at the top of the screen, it would cause the entire 2D cockpit to disappear. If it were a gauge or switch at the bottom of the screen it might only be part of the cockpit. I went round in circles with nVidia of course initially already before I finally found that the utility AvdDisp was the culprit. I was able to disable it by renaming the .DLL file and afterwards everything returned to normal. I'm using AvdDisp with Radar Contact 4 to be able to "make" a window for the command text and undock it allowing me to move it to a second monitor. I don't know if anyone else has experienced this problem yet (?) but hope you might take a look at the utility to see what may cause this. I can provide screenshots of the problem if it would help you visualize the problem. I have talked to nVidia who has indicated that maybe they could get their developer group involved to help solve the issue as I'm sure I won't be the only one to have the problem. I hope you can help as there were no nVidia drivers that could escape this problem. I myself hope to be able to use their 3DStereo driver to produce a 3D rendering of the flight simulator (REALLY COOL!). Thanks in advance for any help. Just point me in the right direction-----> Iven

Howdy Pete, Unfortunately from reading the FeelThere forums it looks as though many have tried to get them to resolve the problem but have run up against a brick wall for whatever reasons (lack of talent or maybe they don't want to fix it, who knows?). Even I had a run in with the forum administrator right off the bat but I pressed to resolve the issue once and for all. Others are now picking up on our findings and it is making a difference at this point. I posted for everyone to do exactly as you described here and so far that seems to be working. I will let them know what you know so if FeelThere "feels" inclined to work this out they can. Most of all we appreciate your help with the FSUIPC side of this...thanks again! :D Iven EDIT: I looked at the other thread you mentioned. That is some of the people in the circles over at the FeelThere forum. That fellow named _ak is one of the programmers or admins and has told us in the FeelThere forums they will not change the logic in the ERJ145 so it looks like the recent version FSUIPC is the only answer for this problem...thanks!

Thanks Pete, I went back and did some further testing and so did the other fellow Steve and it looks like we have a thumb on the problem because he followed your suggestion (it worked) and I disabled the spoiler calibration (and it worked too - even without exiting FS9). The problem now seems not to be FSUIPC (I didn't think so because the spoiler function works with all other payware and freeware aircraft I have loaded) but in the communications with the ERJ program. We are stuck unless the programmers in feelthere take the time to see what the problem is. I made one suggestion, that they make sure the ERJ program disregard any logic coming from the spoiler calibration of your program. That way pilots can still use the calibration for all their other aircraft but it not effect the ERJ. If you are interested here is a link to the specific thread where the details on this problem are located. This has been a long running problem at feelthere with most pilots begging for relief. Thanks for the help and thanks for FSUIPC, it really makes things go a little smoother... 8)

Howdy Peter, Hope to clear something up with your help. I recently started having a problem with my ERJ that many others have the same problems with per forum posts at feelthere. This problem has been ongoing with no resolution. Some do not experience the problem so I decided to spend some time to try and sort this out. I received a copy of a discussion you had with a fellow via the feelthere forum but I have some information to add to this to see if you can help further.... ************************************************************* Let me recap what he posted to me... Hi Iven, Sound's like you are on the correct path. I posted in the Peter Dowson forum about this problem and no one had mentioned it to him before. There was quit a bit of problem's with FSUIPC and the FADEC throttle's the ERJ uses and the way FSUIPC handle's throttle's assignement and calibration, however no one else had reported this spoiler problem to Pete. Here is his answer/response to my question. sulu600 wrote: Hi Peter, Hate to open old topic's and wound's between you and this add-on vendor, however, has anyone mentioned a problem with the complex way the ERJ deploys it ground spoiler/air brakes and a conflict with FSUIPC? You said: There's no wounds that I know of (???)and there's really there cannot be any "conflict" with anything in FSUIPC if you aren't trying to use any conflicting options therein. And to answer your question, no, no one has mentioned any such thing. Sorry. He said: I and several other's who have registered versions of FSUIPC are having trouble with the speed brake's deploying on the ground at speed's above 25 knot's and the throttle's are moved to idle. Once that occurs, the speed brake's deploy (thinking you have just landed and have retarded the throttles) and will not reset. Their cure is to "Remove" the FSUIPC.dll from the module's folder to fix the problem. You said: FSUIPC does not touch the spoiler unless you tell it to, so quite honestly it cannot be anything to do with FSUIPC as such. If removing FSUIPC "fixes" it it can only be because either something else you've set FSUIPC to do is doing it, or another add-in or add-on is operating this through FSUIPC's facilities. FSUIPC is not an "active" component, it only does what it is asked to do. Delete your FSUIPC.INI file so only default options are applied (none of which are related to throttles, axes or spoilers), and check the FSUIPC Log to see what other programs or modules are using it. Eliminate those one by one to find the culprit. You seem to imply that you only get this with registration of FSUIPC -- and since all user-registration really does is allow you to use more options, it is I would have thought pretty obvious that it is most likely to be related to something you have set. He said: I do use FSUIPC to assign one of the axis on my CH Yoke to spoiler, however even removing this has no effect on the problem. You said: FSUIPC does NOT allow you to make any axis assignments. FSUIPC's joystick facilities operate on FS controls, there are no (repeat NO) axis assignments within FSUIPC and never have been. You must be making your spoiler axis assignment in FS, and that is where you have to delete it -- there's no way to make nor delete any such thing in FSUIPC. Regards, Pete He said to me: Hope this help's trouble shooting the problem and I am also getting serious about finding the problem here as well...will keep everyone informed. Steve Park ************************************************************* Okay, I recently found also that if I renamed the FSUIPC.dll that the problem would disappear but went a few extra steps to sort this out. I have a HOTAS Cougar and I too assign an axis to control the speedbrakes on my various aircraft. I do use the axis calibrations under the Joystick tab in FSUIPC. On those aircraft everything works great, it was only the ERJ giving me a fit. So I started playing around and found out something by putting together some things told me by the feelthere folks and further from your comments above... You told Steve above that FSUIPC doesn't assign any axis (I understand this) but there is under the Joystick tab pages to calibrate the various axis' on a joystick and throttle and such. So I figure some sort of interaction was happening there? I think many people have gone in and disabled various settings trying to isolate the problem with no luck but this failed because of something further I stumbled upon. I did the same thing with the same results, the speedbrakes wouldn't work after disabling certain FSUIPC settings. The feelthere folks stated that the logic in the ERJ worked primarily on/off (fully deployed or fully retracted) and not on graduated axis control. So I concentrated on this. While messing around with the settings in FSUIPC the ERJ speedbrakes started working but I didn't know how or what I had done so I set out to duplicate this. I went back in and started messing around again and sure enough got it to screw up again, that was easy. Now the trick was to get it working again...what fun :D The trick I found was in restarting the flight simulator AFTER making the changes in FSUIPC. The setting in FSUIPC that seems to be in conflict is the speedbrake axis calibration. Click reset (for the speedbrake axis calibration), exit FSUIPC and flight simulator then restart and all was back to normal. I don't know if you can look at anything here or if the folks at feelthere will talk to you about this (I did ask them to coordinate with you on these findings) but I can imagine if this problem could be fixed once and for all there would be some mighty happy ERJ pilots around... Regards, Iven