|
Post by clive6354 on Feb 22, 2020 13:55:09 GMT -5
The first option does not make any difference. The second option mess up my monitors too much. When I do run the program in 640 X 840 the application window I observe still shrinks in size and resolution is not acceptable. Have you looked into my other comments regarding the procedure
I do not have any problem with the size of the application window in the previous version V1.5
|
|
|
Post by Matthew King on Feb 22, 2020 14:41:31 GMT -5
The first option does not make any difference. The second option mess up my monitors too much. When I do run the program in 640 X 840 the application window I observe still shrinks in size and resolution is not acceptable. Have you looked into my other comments regarding the procedure I do not have any problem with the size of the application window in the previous version V1.5
Are you using windows 7 or 10? You have something very unique going on with your monitor setup; we'll get it sorted out though. Just need to find out what's happening. It's got to be a scaling option somewhere... Concerning the procedures, I explained them in the video; your copilot is following Boeing recommended procedures.
|
|
|
Post by Matthew King on Feb 22, 2020 14:50:26 GMT -5
If it's Win 7, try the above but this time "Disable Desktop Composition." Essentially, we're trying to prevent your system from redrawing (scaling) the application based on your settings. I'm really trying to avoid any hard code changes because this appears to be an isolated issue; so, while trying to fix the problem for you, I may break hundreds of other's application. There is a solution though...I know it! I wish I could troubleshoot myself but I can't recreate the issue.
The desktop composition visual experience feature, introduced since Vista, fundamentally changed the way applications display pixels on the screen. When desktop composition is enabled, individual windows no longer draw directly to the screen or primary display device as they did in previous versions of Windows. Instead, their drawing is redirected to off-screen surfaces in video memory, which are then rendered into a desktop image and presented on the display"
|
|
|
Post by clive6354 on Feb 22, 2020 14:52:49 GMT -5
Windows 10
Yes the procedures are correct but if you read my message where I explain that the First officer is not setting the switches correctly. e.g Why are the IRS switches being set to ATT ?? and during pre flow check why is the engine 2 start switch set to continuos before engine start
|
|
|
Post by clive6354 on Feb 22, 2020 15:21:14 GMT -5
Would you like me to produce a video to demonstrate how the first officer is setting the switches during the Pre Flow startup and start engines procedure
|
|
|
Post by Matthew King on Feb 22, 2020 15:26:29 GMT -5
I'd really like to focus on the scaling issue; this concerns me. If I could impose on you one more time
Right-click on FSFO.exe Select Properties Click on the Compatibility tab Click Change high DPI settings Check "Override high DPI scaling behavior..." Select Application (this limits the setting to FSFO only)
Are you starting 737 in cold and dark state or something else?
|
|
|
Post by clive6354 on Feb 22, 2020 15:33:40 GMT -5
As I have stated in my previous messages COLD & DARK (any other setting would produce a false operation from the program)
|
|
|
Post by clive6354 on Feb 22, 2020 15:44:59 GMT -5
Right-click on FSFO.exe Select Properties Click on the Compatibility tab Click Change high DPI settings Check "Override high DPI scaling behavior..." Select Application (this limits the setting to FSFO only) Part success, the application windows remains the same size, however the bottom portion of the application window is cut off and only the top half of the word CONNECT is showing, therefore the bottom panel has been cut in half
|
|
|
Post by Matthew King on Feb 22, 2020 16:50:25 GMT -5
View AttachmentRight-click on FSFO.exe Select Properties Click on the Compatibility tab Click Change high DPI settings Check "Override high DPI scaling behavior..." Select Application (this limits the setting to FSFO only) Part success, the application windows remains the same size, however the bottom portion of the application window is cut off and only the top half of the word CONNECT is showing, therefore the bottom panel has been cut in half Finally, progress! Ok, using the steps up, also click on "Use this setting to fix scaling problem..." Both of them together should fix the issue; one for the form and the other for the font. Again, this doesn't change any of your display settings, just the setting for the application specifically.
|
|
|
Post by clive6354 on Feb 22, 2020 17:19:34 GMT -5
No success on "USE SETTING TO FIX SCALING PROBLEM"
|
|
|
Post by clive6354 on Feb 22, 2020 17:42:21 GMT -5
Hi Matthew
I purchased First Officer Pro when it was first released and have not been able to use it fully. Despite having difficulties with the application window shrinking on start of the program I have also had difficulties with the First Officer setting switches to unworkable settings. As stated in my previous messages all my tests have been carried out using a cold and dark setup. Considerable time has been used trying to resolve the size of the application window and my other difficulties have not been addressed as yet. As I have been patient trying to resolve problems it appears that all is not well, therefore as I have purchased a product that I am unable to use fully please would you make arrangements to refund the amount I paid for the program and I will return to using FS2CREW
|
|
|
Post by Matthew King on Feb 23, 2020 14:53:30 GMT -5
Hi Matthew I purchased First Officer Pro when it was first released and have not been able to use it fully. Despite having difficulties with the application window shrinking on start of the program I have also had difficulties with the First Officer setting switches to unworkable settings. As stated in my previous messages all my tests have been carried out using a cold and dark setup. Considerable time has been used trying to resolve the size of the application window and my other difficulties have not been addressed as yet. As I have been patient trying to resolve problems it appears that all is not well, therefore as I have purchased a product that I am unable to use fully please would you make arrangements to refund the amount I paid for the program and I will return to using FS2CREW I understand your frustration, Clive...I don't like leaving problems unfixed. I can defiantly work with you on a refund; however, I respectfully ask for your help to solve this problem. I have two ideas that won't consume more than 5 minutes of your time. First, can you change your DPI scaling to mimic the settings in the attachment? We did that yesterday but I forgot to tell you to select System (Enhanced) vice Application. If that doesn't work, I have written a method to rescale the application based on DPI vice Font settings. I'll upload today; if you wouldn't mind trying I'd be internally grateful! As for the switches, that's an easy fix once we get the form sorted. Again, this is a whole new application; obviously, there are some growing pains. I won't ask for any more assistance beyond what's listed there... Attachments:
|
|
|
Post by clive6354 on Feb 23, 2020 16:31:48 GMT -5
SUCCESS..that has worked. The application panel is how it should be
Please would you now go through the problems I am experiencing with the First Officer setting switches and knobs incorrectly? The problems I am experiencing are all performed from a COLD & Dark setup. Your video explains the procedures correctly but for some reason the program is not performing correctly. I will list the items that I wish you to investigate When the GPU starts a message flags up in a bar at the top of my monitor "Problem detected with GPU" When the IRS is being set up, why are the switches set to ATT mode and not Align? Why are the packs not set correctly (configured for engine start) before the engine start procedure is commenced? When theFirst Officer begins his PRE FLIGHT FLOW. Why does he set No 1 engine start selector switch to GRD and No 2 to CONT. When the First officer is starting engine 2 the engine selector switch goes from CONT to OFF. The first officer continues oblivious that there is something wrong. After No 1 engine is selected to GRD the procedure continues with a message that both engines are stabilised. BOTH ENGINES ARE OFF and the packs were not set correctly. Would it be possible to amend the program so that it would not be possible for the First Officer to go through the process of starting the engines without the packs being set correctly? At the moment with the packs on I can instruct the First Officer to start engines and he will go through the process oblivious that the packs are not set correctly
|
|
|
Post by Matthew King on Feb 23, 2020 20:17:55 GMT -5
SUCCESS..that has worked. The application panel is how it should be Please would you now go through the problems I am experiencing with the First Officer setting switches and knobs incorrectly? The problems I am experiencing are all performed from a COLD & Dark setup. Your video explains the procedures correctly but for some reason the program is not performing correctly. I will list the items that I wish you to investigate When the GPU starts a message flags up in a bar at the top of my monitor "Problem detected with GPU" When the IRS is being set up, why are the switches set to ATT mode and not Align? Why are the packs not set correctly (configured for engine start) before the engine start procedure is commenced? When theFirst Officer begins his PRE FLIGHT FLOW. Why does he set No 1 engine start selector switch to GRD and No 2 to CONT. When the First officer is starting engine 2 the engine selector switch goes from CONT to OFF. The first officer continues oblivious that there is something wrong. After No 1 engine is selected to GRD the procedure continues with a message that both engines are stabilised. BOTH ENGINES ARE OFF and the packs were not set correctly. Would it be possible to amend the program so that it would not be possible for the First Officer to go through the process of starting the engines without the packs being set correctly? At the moment with the packs on I can instruct the First Officer to start engines and he will go through the process oblivious that the packs are not set correctly Awesome! Ok, I'll get to work on the switches; this shouldn't be too difficult to correct. First, would you mind downloading and installing the current version of FSUIPC? FSFO uses FSUIPC to check to see if the switches are set in the correct potion. Mr. Dawson upgraded FSUIPC to account for both the 737NGX and NGXu; if you're using FSX, the current version is 4.974; P3D is 5.153. I just went through the code and looks right. Regardless, I can do other things to force a recheck of the systems you listed above. Can you try the FSUIPC and report back? We can get this portion fixed fairly easily. We'll get you fully up soon! Thanks for you help with the DPI issue!! Matt
|
|
|
Post by clive6354 on Feb 24, 2020 2:27:54 GMT -5
I do have the current version of FSUIPC installed 5.153
My system has all current drivers, programs and updates
P3D v4.5 All PMDG aircraft (at the moment I am using the 737NGX) FSUIPC 5.153 (registered) Windows 10 (updated)
i7-7700 (4.2) GTX 1080
|
|