The A2A Simulations Community

Hi Joe & Shousa

Downloaded DirectX from this link. It appears to install successfully. I don't get any error messages installing it. I went through the installation process in both normal and safe modes. It goes through without a hitch and tells me that it is ready to work.
However, when I try to reinstall the Spitfire, it still goes looking for DirectX and comes up with the same error message when it tries to install it. The Spitfire has the same problems when I try to fly it.
The 'netframwork' appears on the program listing, but there's nothing on it that I can recognise as DirectX. I can't be sure, but it looks to me like this thing does'nt install, in spite of the installation process appearing to succeed.

Regards- Robert

Do you have the Microsoft.Net Framework 3.5 or better installed all so check the your sim connect is not broken

If you check your Control Panel go to Programs and Features it is in Alphabetical order and it is there Microsoft.Net Framework 3.5
just reinstall it just in case it has some problems

http://www.microsoft.com/net/

_________________
Ron
B-17 AIRFRAME 710 HRS PLUS AND CLIMBING




GIGABYTE X58A-UD5 MB, INTEL I7 950, 12GB DOMINATOR-GT DDR3 RAM, WIN7 64, GIGABYTE SUPER OVER CLOCK GTX 560 TI 1GB GGDDR5 1000Mz, CORSAIR 850W PS, NOCTUA NH-D14,
TRACKIR 5 & TrackClipPro

Hi Norforce

Netframework 4 appeared on the listing. I reinstalled it as suggested. I then went into Safe Mode and reinstalled DirectX (apparently successfully) and then the Spitfire. The result was no change. The Spitfire installation still tries to install DirectX and fails. The Spitfire has all of the original issues when it flys.

It has occurred to me that DirectX is to do with graphics. The Spitfire doesn't appear to have any graphics issues (the graphics appear superb). The issues are to do with controls and one of the sound effects.

Regards- Robert

Robert,

When you get to the "directX " part of the Spitfire install, have you tried just "cancelling" it and then hitting "finish"?

D

_________________

...Some say he never blinks, and that he roams around the woods at night foraging for Merlin parts...

Hi Darryl
Affirmative! The installation appears to finish successfully. However, when flown, the Spitfire has the problems outlined in my original post. These are-
(1) No propeller speed control (on the Mk2), although the cockpit lever moves.
(2) No pitch trim control from the external controller (although the keyboard and mouse will operate it).
(3) No sound effects on undercarriage extension/retraction.
The graphics appear to be superb, which makes me wonder whether these really are DirectX problems.
Regards- Robert

Robert,


Ok, another question...with the Mk II have you been into Shift 7 and ensured that it is fitted with the ROTOL airscrew? If it has the Watts FP on it, then the cockpit control will work but will, obviously, not change the pitch.

Direct X is graphics..but that does not mean that the problems it can cause are limited to graphical ones. I've had many different problems thta have been solved by getting it going.

The pitch trim controller is strange but my external radiator shutter lever just stopped working for no apparent reason a while back. It turned out to be the Configurator failing. It is being looked in to as soon as I have time to test a couple of things. This sounds like it may be a similar problem.

Do you use FSUIPC? It is a "module" by Pete Dowson that makes controllers much easier to assign..amongst other things.

The sound effects I can't help with but we will keep plugging away.


regards


Darryl

_________________

...Some say he never blinks, and that he roams around the woods at night foraging for Merlin parts...

This is a tricky one. As far as your similarities to mine: I installed the Spitfire prior to downloading the latest Direct X. After installing said Direct X the Spitfire worked. Don't try reinstalling the Spitfire after your Direct X download... Aka do the Spitfire first.

If that is not the case: Do you have the most recent drivers for your graphics card and sound card? I doubt these would be your problem, but its worth checking...

Last guess: Maybe delete the DXError.log and DirectX.log files prior to reinstalling? Don't do this unless someone else says its ok (I'm a computer idiot), but maybe they don't get overwritten in a new install and might have a bad effect?

I wish I could be more help!

Joe

_________________

Hi Joe & Darryl
Finally getting somewhere! I updated the video driver software and installed a couple of Netframework 4 updates.

I hadn't yet reinstalled the Accusim pack. When you select the Mk2 Spitfire from the menu, the rotating image always appears with a 3 bladed propeller. However, when the flight starts, it seems that the default propeller is of the 2 blade, fixed pitch variety. You don't necessarily notice this unless the engine stops. (I guess it begs the question as to why an aircraft with a fixed pitch propeller would have a propeller speed control in the cockpit.)

I next reinstalled the Accusim pack and changed to the 3 blade propeller. That all now works fine and the undercarriage extend/retract sound effect has mysteriously come good.

The only problem remaining is the external elevator trim controller. It works fine on every other aircraft. However, it seems that this particular function is the only on that needs to be selected on the Spitfire Configurator panel. It asks me to select the path to the main FSX folder. I select- Computer/C Drive/Programs/Microsoft Games/Flight Simulator X.

I can then make the required selection on the panel. However, when I try to save it I get an error message. It says that the pathway to FSX is incorrect or the Spitfire hasn't installed correctly.

Is DirectX still at issue ? Is it installed ? Does it matter ? I guess the important question now is whether I'm doing anything wrong operating the Configurator Panel ?

Regards- Robert

The easy answer is that the Mk II was built that way but could have a fixed pitch Watts fitted..leaving the control "dead" in the cockpit. I was, historically, against the Watts being available on teh Mk II but the Universal Spline on the Merlin XII technically could have taken one, so it was thought by A2A to be a neat option (and on that basis I agree). I am not aware of any instance where that actualy happened though.

I'm not sure about DirectX but it could be causing your configurator issue....what OS do you use, Win 7, 32, 64,? XP, etc?

One thing with Win 7 is that the directory structure is different and configurator may have to be pointed at the "programs x86" directory (Ithink that is the one / or proper name for it.)

It sounds like you are doing the configurator entry correctly but a non-standard directory is stopping the entry "finding" FSX.

Glad we are starting to "get there".

It may well be worth your while investing in FSUIPC..it is a great way to run controllers and is pretty cheap too. I can help you with LUA Scripts etc to run just about any control you like from joystick buttons.

Darryl

_________________

...Some say he never blinks, and that he roams around the woods at night foraging for Merlin parts...

Hi Darryl
My operating system is 32bit Windows 7. Can't find a directory called 'programs x86'. A search comes up with no result. Can you tell me what it is and where it should be ?

FSUIPC sounds interesting. I've built my own replica Spitfire and Mustang controllers. It would be great to have proper control of things like magneto switches and potentiometer control of functions like rudder and aileron trim instead of having to use switches. Who sells it ?

Regards- Robert

I don't think you will find the ( programs x86 ) folder in a 32 bit sys its only in the 64 bit sys

_________________
Ron
B-17 AIRFRAME 710 HRS PLUS AND CLIMBING




GIGABYTE X58A-UD5 MB, INTEL I7 950, 12GB DOMINATOR-GT DDR3 RAM, WIN7 64, GIGABYTE SUPER OVER CLOCK GTX 560 TI 1GB GGDDR5 1000Mz, CORSAIR 850W PS, NOCTUA NH-D14,
TRACKIR 5 & TrackClipPro

Robert,


I am buried here at work...but try the Registry Repair Tool fix here (thanks Lewis!!) :
http://www.flight1.com/view.asp?page=library it is safe and effective.

Sorry if this has already been suggested.....


I'll answer the rest later mate,

Darryl

_________________

...Some say he never blinks, and that he roams around the woods at night foraging for Merlin parts...

Thanks Darryl (and Lewis)
Didn't have much luck with the Registry Repair tool Kit. It asks me to browse for FSX.EXE. When I do that I'm only asked to open it. However, when I click on open, nothing happens. I can't seem to get it to procede.
Regards- Robert

Robert,

It may be time to see if we can hook up and I can demonstrate how little I know personally, rather than by "forum"

Seriously, I would like to try to figure out the registry tool problem, because THAT is very stange..and my be indicative of the wider problem?


Chat by skype, Team Speak server, PM back and forward here as we work..something like that? I'd love to be able to get you up and going.

Darryl

_________________

...Some say he never blinks, and that he roams around the woods at night foraging for Merlin parts...

Just to mention that the Flight1 registry repair tool simply resets the path to FSX.exe correctly in the required keys in the registry. It asks you to give the location of the fsx.exe, you click on OK or something, and all is good, that is it, it does nothing else...

Apparently the key can be corrupted by various things and strange things can occur if the key is corrupted (for one, PMDG planes have difficulty tracking the FMS magenta line or ILS paths are incorrect...)

Hope this helps with that little bit at least...

Andrew

_________________
i7 2700K @ 4.8GHz on air (NH-D14), ASUS MAXIMUS FormulaV, 8Gb DDR3-2133MHz
EVGA GTX670 2Gb, Windows 7HP on RaptorX 300, FSX on OCZ Vertex2 240Gb SSD