von

Pete, "So something is different, either in your P3Dv3 setup or in Windows. That's a puzzle and a difficulty, because I cannot really help without being able to have it go wrong here." I checked again ... and found the issue. In windows. My new PC .. Basically default settings / setup ... User Account Control was not turned OFF.

I tested again. If P3Dv3 has focus (full screen or windowed) then keyboard key F8 or FSUIPC yoke button does not take a screenshot. If I click on my second monitor screen (not in P3Dv3 focus) then the keyboard key F8 and FSUIPC yoke button takes a screenshot OK.

Pete, Thanks for checking. I use Win7-64 .. new PC with P3Dv3 only now. All worked ok with my Win7-64 and prior versions of FSUIPC and prior versions of FS9, FSX, FSX Acceleration, and P3D (up to v2.5 but not 3.0 now). I have used Screenshot utility - payware for years now with FSUIPC assigned yoke button (key=F8) for taking screenshots during my flights. When not using Flight Sim(s) I press the Keyboard F8 key to take random screenshots .... except for other programs that trap F8 for their own use. http://www.screenshot-utility.com/

Hello, I have a screenshot program. I press F8 to take a screenshot. Screenshots taken ok in Windows7-64 desktop. I have P3Dv3 on a new PC. I unassigned F8 (flaps down) key in P3Dv3. I set a yoke button to F8 key in FSUIPC v4.947c When I press F8 in P3Dv3 it is not passed to Windows. No screenshot taken. Should F8 be passed to Windows to do the screenshot FSUIPC v4.947c? Note: All ok on my previous P3Dv2.5 and previous FSUIPC version(s) setup but I no longer have it on my system. [buttons] PollInterval=25 ButtonRepeat=20,10 1=R1,32,C65734,0 2=R1,36,C65735,0 3=R1,34,C65672,0 4=R1,38,C65671,0 5=P1,19,K190,10 6=P1,5,C65758,0 7=P1,4,C65759,0 8=P1,0,K119,8

I just checked now .. using FSX Acceleration, Win7-64, EMB 175 all ok with Wx radar.

fswxr-2100 Yes, I have it in FS9 and FSX. Many pilots thought there was a problem with the FT WX radar ...... but all is ok.

I purchased it back in 2010. "I think It may have something to do with FSUIPC and the FSWXR gauge not working. " What is FSWXR?

"Does not work in fsx or fs9 on my system, as well tested it on another windows 7 machine as well as an older windows xp box, Nothing!" Do a video (or close up screenshots) showing your steps to activate the Wx radar.

I got the fatal error also: Last thing I did was update FSUIPC to v4-939c ********************************** Log Name: Application Source: Application Error Date: 2/28/2015 3:19:51 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: homesv1 Description: Faulting application name: Prepar3D.exe, version: 2.5.12943.0, time stamp: 0x54e39da6 Faulting module name: weather.dll, version: 2.5.12943.0, time stamp: 0x54e39d37 Exception code: 0xc0000005 Fault offset: 0x0001175c Faulting process id: 0x638 Faulting application start time: 0x01d0539377ca8a77 Faulting application path: F:\Lockheed Martin\Prepar3D v2\Prepar3D.exe Faulting module path: F:\Lockheed Martin\Prepar3D v2\weather.dll Report Id: 25b84ad8-bf87-11e4-9e6e-50e5493a5064 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-02-28T20:19:51.000000000Z" /> <EventRecordID>693871</EventRecordID> <Channel>Application</Channel> <Computer>homesv1</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>2.5.12943.0</Data> <Data>54e39da6</Data> <Data>weather.dll</Data> <Data>2.5.12943.0</Data> <Data>54e39d37</Data> <Data>c0000005</Data> <Data>0001175c</Data> <Data>638</Data> <Data>01d0539377ca8a77</Data> <Data>F:\Lockheed Martin\Prepar3D v2\Prepar3D.exe</Data> <Data>F:\Lockheed Martin\Prepar3D v2\weather.dll</Data> <Data>25b84ad8-bf87-11e4-9e6e-50e5493a5064</Data> </EventData> </Event> **************

Thomas, "And of course all aircrafts do exist in the new version." Initially I will not have all my aircraft installed ... after just installing P3D V2.5 I may have to wait for vendors to approve their aircraft in P3Dv2.5 before installing. So, I must wait until all aircraft ar re-installed before using my old Profiles and ini file?

Using FSUIPC Version 4.939 and P3D v2.5. Can I copy my old P3D v2.4 FSUIPC Profiles folder and the FSUIPC4.ini to the new p3d Modules folder or do I have to setup all aircraft axes / buttons etc. again to build new files?

Scobie, It is very sad .. the hours of work you personally did supporting the products. Thanks for the follow up here. Have a good day.

Sorry to hear that. But always thought forums had backups of their data.

I do not see any posts from 2013 .. where did they all go?

I did a short video (HD 1080P) FeelThere EMB 175 weather radar (FSX)

What does it look like in FSX "windowed" mode? List here the resolutions that are available on your laptop display? List here the resolutions that are available in FSX Options/Display section. Maybe the developer can tell what is missing for you in DAYlight VC .. because you Nighttime VC is OK?

Which version of Windows? FSX Windowed mode or full screen? If you zoom in does the panel look good?

What is you resolution? Do you use only one monitor? If you would like to see a specific screenshot (JPG) I could do one. Are your grainy frm McPhat, Feelthere house livery or both? What is your Windows / version?

Today I fley the ERJ145 KTOL-KORD. FD bars work just fine on departure. I did several departure screenshots. This one I had dialed SPD VR+20.

I took a look (short video) at various (VC and spot views) FSX FT-ERJ135 nighttime lighting this morning. I use Win7-64 Is this what you see?

Pete, Thanks for the answer.

Pierre-Jean, Sorry, I do not know about FSCOPILOT .. you have to contact the developer.

Pierre-Jean, Post a copy of your last FSUIPC4.log file .. from when you had an error. As a test, try this: ******************************************************** <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> <Launch.Addon> <Name>IvAp</Name> <Disabled>False</Disabled> <Path>D:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll</Path> <Commandline/> </Launch.Addon> <Launch.Addon> <Name>FSCopilot</Name> <Disabled>False</Disabled> <Path>Modules\FSCopilot.dll</Path> </Launch.Addon> </SimBase.Document>

Pierre-Jean, 1. Go to your Modules folder and delete the LoaderDLL file 2. Edit this file to remove the _Loader part. <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4_Loader.dll</Path></SimBase.Document> **** <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path></SimBase.Document>

I am using windowed mode. When I select logging to the screen (free memory) it is displayed in the same position (overprints) as FPS and other FS data. Is there a way to move either the FS data or FSUIPC data a few lines down so both can be seen without one overprinting the other?