iainsmith

That's it Steve - you've fixed it! I had C\Program Files\Steam and it should have been C\Program Files (x86)\Steam.
 
Now I have installed the libraries without problem and when I run diagnostics I get four HINTS all related to VC shadows - e.g. "ForceVCShadowMap not set in cfg, VC shadows will only be shown when it is set in VC model" and "A/craft self shadowing not set in cfg, VC shadows will not be shown".
 
I am not too bothered about VC shadows so I am happy. Thanks for your excellent support.
 
Iain

Got my traffic back in FSX-SE on Win 10. How? Simply by re-installing all my WoAI files in spite of them being a mix of FS9 and FSX traffic files.
 
I must also say I'm getting very good frame rates and smoothness with Win 10 in DX10. I'm going to purchase Steve's DX10 fixer.
 
Iain Smith

Thanks Joe. I've now installed a few of those that I didn't have.
 
Regards
 
Iain

Ok having said the topic was closed and that I was going to uninstall/reinstall I decided to have one more go, to try and find a reason/solution for future reference.
 
I reasoned that as the message keeps referring to a plan that it doesn't like there must still be a file for that route. I went into FSX/PMDG/PMDG777X/PanelState. In there I found a couple of files that I had missed, that related to the saved flights that had failed to re-load. I deleted those files started FSX got the spinning microlight, selected the 777 I wanted, the airport and time of day and everything started up normally. Problem solved!
 
Iain Smith 

Problem solved! I after weeks without RC I went back to an earlier version of FSUIPC. Instant success!
 
Yes, I know - shock! horror! I'm not using the latest version.
 
It's highly likely that my copy got corrupted. I'll d/load and install the latest in a few days but right now I'm enjoying having RC back and am reluctant to jeopardise that! :rolleyes:
 
Iain Smith

@ Ray & Ron
 
This is very strange. Using a default 737 I parked at Prestwick (default airport) and set up an FSX plan to another default airport Dublin. Fired up RC4 (folder now in C:\rcv4x, FSX is on the F drive) selected the FSX plan and started RC4. Everything fine, just as it should be and for the first time in days I heard RC voices, including your dulcet tones, Ray.
 
So, I changed aircraft to my recently acquired Aerosoft Airbus X Extended and re-selected the same flight plan. Again everything was fine, as it should be with a full response from RC.
 
I then decided to try what I've been trying for days. I relocated to Heathrow with the A320 to T5, gate 513 created a plan in FSX from LHR to Hamburg. Fired up RC4, selected that plan and started RC. Everything fine, as it should be - full response from RC4.
 
Then the final test. Closed down RC4. Fired it up again and this time selected the plan I had previously created to Hamburg in FSBuild. Started RC and everything fine just as it should be.
 
So, it looks like I'm good to depart LHR for Hamburg at last.
 
I'm mystified as to a) what was causing the problem and b) what put things right. Having run makerwys I would have expected, if that was the problem, for it to have been corrected straight away not several attempts later. The same with moving RC out of the Prog Files folder.
 
Anyway, thank you both for your time, patience and help also the others who responded to this thread.
 
Regards
 
Iain

Hi Florian, I loved your Fokker airliners for FS9. I take it you never finished the VC so it could be used properly in FSX?
 
Yes you are right - clicking somewhere on the panel or possibly screen brings back the zoom capability. Thanks.
 
Iain Smith

@ GACSavannah (Kerry). My apologies for dismissing your suggestion. You were on the right track except it's not just the window but anywhere on the screen that does the trick.
 
Iain