didjmaster

I am a simulator pilot only, with over 4 years experience (not new to FS or a variety of aircraft - payware or stock planes that came with the game). I have been flying the V35B from Carenado with FSX for about 2 months now, and it is still giving me some issues on landing, specifically ballooning and bouncing. I am being very careful to meet the suggested airspeeds and configurations as posted in the POH and the landing checklist; however I still can't get a smooth landing. Is anyone else experiencing this problem with this specific aircraft? I am not a real-world pilot, so I don't have experience in this plane to compare with the simulation, but I have done a lot of research on landings (and specifically what may be responsible for "ballooning" and other common landing errors). I have no trouble with landings on other aircraft (light or heavy), even if I haven't flown them in over 6 months. While I am always trying to refine my skills, I am just finding a smooth landing in the Bonanza to be too much work. I will, no doubt, continue to learn more about landings and landing errors (as well as log some more time with this aircraft). But I wanted to ask these questions before I dive any deeper than may be necessary. Could there be a problem with the design of the Carenado V35B, or is the experience realistic to a real-world V35B? Is there something that I should know about the particulars of this aircraft, so that I can better adjust my approach toward better landings? Thanks!

Okay, I was able to fix the issue.Yes, it was a registry error, however it was one that seemed to have affected my whole computer. The registry repair utility was not able to fix it, so I had to resort to another registry repair tool, which did fix it.The main error I was having was that I needed to re-install FSUIPC (common error for addons). It somehow got messed up when I first installed the Wilco 737 PIC. The registry errors, however, were making it impossible to reinstall FSUIPC. I was getting errors relating to "untrusted publisher" in conjunction with FSUIPC.I fixed the registry errors (took about 3 hours), re-installed FSUIPC, and then fresh install of FS2Crew. Now it works. And I knew it was going to work this time because upon loading FSX, I saw (for the first time) a window that asked to verify and allow the guages for FS2Crew. I hadn't seen these before, and with my experience of installing gauges in the past, I knew I was on the right track.Thanks for the comments guys. As always FSUIPC seems to be the make or break portion of addons. I wish that I didn't have to re-install it every 3 months because of addons, but oh well.

Yes, SP1 is installed. also I am running Windows XP is that is relevant.

I am having some issues getting the Main Panel and Configuration Panel to show for the Wilco 737 PIC. I see the RMI guage, but it does not do anything when I click it. If I click on the alt tab and go to View-->Instrument Panel, I see that those panels are available (this it the only way I can get to the them). But then when I try to bring them up, all I see are black boxes.I know this is addressed in the manual, and I have tried to re-install the program, but to no avail. I also tried to copy the panel.cfg files over to the individual planes' panel cfg files, but I see that there is no discrepancy between the two. So, what ever is supposed to be in the panel.cfg file of each of the planes is already there. For me I have gauges 15 and 16 reserved for these 2 panels in the .cfg file. I guess the images for the Main Panel and Configuaration Panel just didn't get copied over some how. Any help resolving this would be great!