Any attempt to click on the radios in the MAAM rd4 or Briefing time results in an immediate freezing and shutdow of FSX. SP2 is installed.If I set the radio frequencies in another plane, non MAAM, then transfer back the radios work OK and the FSX shows no distress.This problem appeared suddenly without any discernable cause. Radios worked fone for years.I uninstalled and reinstalled SP2 without any result.Any ideas?HP

Any attempt to click on the radios in the MAAM rd4 or Briefing time results in an immediate freezing and shutdow of FSX. SP2 is installed.If I set the radio frequencies in another plane, non MAAM, then transfer back the radios work OK and the FSX shows no distress.This problem appeared suddenly without any discernable cause. Radios worked fone for years.I uninstalled and reinstalled SP2 without any result.Any ideas?HP

Hi,I have osted a problem with the R4D Radio panel as well under CAL2024. I have yet to recieve any concrete resolutions and hope to do so soon. II have tried reloading several times in windows 7, FSX. I have since purchased the DC3 version from Just Flight 1 and it will only show their great inst panel in virual cockpit, but does only show the DEFAULT DC3 panel in 2D. I am getting to think it may be associated with either windows 7 or the dual core set-up. My thoughts only as I am not a PC wizz. I just wanted to let you know there is another individual with the same issue.CAL2024

Cal2024Thanks for the info. Perhaps someone from the MAAM team will get on this. They're products are great, but it's pesty not having the radios. I also reinstalled the aircraft.Fortunately I'm not experiencing the other problems that you mention.My setup:Vista Home Premium 64 bit3.2 ghz Intel Core i7 9656136 MB Installed MemoryATI Radeon HD 4870 X2 Display Adapterhprass

Sorry you are having this problem, hprass. It's most interesting to me that you experienced this issue suddenly, after a long period of normal operations. This would seem to back-up what I have thought for some time, that there is a conflict elsewhere in FS, caused by a change, like the installation of another add-on, that somehow causes this bug to crop up. Was there another add-on or program that you installed just before this happened? I also wonder if you and CAL2024 have some common factor. I don't think it has anything to do with Win7 or dual-core, both of which I have, myself, with no issues. BTW, Cal, that "other DC-3" does not have a 2D panel and uses the default DC-3 panel. Peculiar, but not unique to your system.

Sorry you are having this problem, hprass. It's most interesting to me that you experienced this issue suddenly, after a long period of normal operations. This would seem to back-up what I have thought for some time, that there is a conflict elsewhere in FS, caused by a change, like the installation of another add-on, that somehow causes this bug to crop up. Was there another add-on or program that you installed just before this happened? I also wonder if you and CAL2024 have some common factor. I don't think it has anything to do with Win7 or dual-core, both of which I have, myself, with no issues. BTW, Cal, that "other DC-3" does not have a 2D panel and uses the default DC-3 panel. Peculiar, but not unique to your system.

rambowThanks for the info. Now at least I should not be looking for a 2D panel for the just Flt DC3. Also I will try to rethink my installations as this is a brand new PC for me and has very little else on it, but could have been a previousm instal thqat I tried to bring in fromfs9. So, to restart my new PC from scratch is not a seriuos issue. Thanks again!CAL2024

Might not solve your problem, but check out this thread over in the PMDG forum http://forum.avsim.net/topic/330308-consistent-fatal-error/. Newer systems can be impacted by a problem with uiautomationcore.dll that causes crashes when switching windows - might be what's happening here?

Might not solve your problem, but check out this thread over in the PMDG forum http://forum.avsim.n...nt-fatal-error/. Newer systems can be impacted by a problem with uiautomationcore.dll that causes crashes when switching windows - might be what's happening here?

HI, i have discovered the problem and has now been rectified and checked . The problem was not observing the installation address. The auto installer put the address in the destination block, but I neglected to observe the beginning of the address block, which said "C/Program files/Microsoft simulator X" for which the address should be changed to "Program files (x86) / Microsoft flight Simulator X". I hope this fixes the others who have been torn over this issue. Problem Solved!! CAL2024