Search found 45 matches

by mk882004
27 Mar 2021, 19:25
Forum: ProsimUtils - by Wpslider
Topic: Printing private Vpilot messages (PDCs)
Replies: 0
Views: 106

Printing private Vpilot messages (PDCs)

Good Afternoon,

I recently installed a printer with PSU, and all works perfectly with ATIS's, METARs, TOPcat data, PFPX data. But when I receive a Vpilot private message, like a PDC for example. The print button is available, but nothing will print when I press it.

Is there a way to print these types of messages, and if so what am I doing wrong. Or is this function not available.

Thanks,

Matt
by mk882004
04 Dec 2020, 21:22
Forum: ProsimUtils - by Wpslider
Topic: vPilot Disconnected with 1.8.1 (Resolved)
Replies: 1
Views: 160

Re: vPilot Disconnected with 1.8.1 (Resolved)

Well, as with everything it seems, it was a properties issues, right click go to Properties, and ensure that the box on the bottom right "UNBLOCK" is checked, mine wasn't, as soon as I clicked that, I loaded it up, it asked for the IP address, and now it is green!
by mk882004
04 Dec 2020, 17:13
Forum: ProsimUtils - by Wpslider
Topic: vPilot Disconnected with 1.8.1 (Resolved)
Replies: 1
Views: 160

vPilot Disconnected with 1.8.1 (Resolved)

Hey guys, I just updated PSU to 1.8.1 with Prosim 3.01b16. Everything is connected and working properly except vPilot.

I've uninstalled vPilot and done a fresh install, installed the plugin to the plugin folder configured the config file with the appropriate IP address.

I'm not sure what I'm missing here, I've attached the PSU log for reference, any help is greatly appreciated, thank you.

Matt
by mk882004
13 Aug 2020, 19:09
Forum: ProSimB738 - Technical support - software related
Topic: Unable to Detect Path to Simulator Building Database (RESOLVED)
Replies: 8
Views: 746

Re: Unable to Detect Path to Simulator

Thanks for the tip, I put everything back to the way it was after it didn't work, so there has to be something else going on with it.
by mk882004
13 Aug 2020, 14:40
Forum: ProSimB738 - Technical support - software related
Topic: Unable to Detect Path to Simulator Building Database (RESOLVED)
Replies: 8
Views: 746

Re: Unable to Detect Path to Simulator

I appreciate your help Willow,

I did check all the permissions, and ensured that all those folders aren't blocked, and gave full control to everyone, that didn't work either.

When you say install in a different directory, do you mean the entire simulator in a different area? This would require a clean install I'm assuming? Any suggestions on where to put it?

According to the release notes, they changed something with the scenery database with v2.29, and that is where the issue began, so somebody at prosim must have an idea.

Thanks,
by mk882004
13 Aug 2020, 14:01
Forum: ProSimB738 - Technical support - software related
Topic: Unable to Detect Path to Simulator Building Database (RESOLVED)
Replies: 8
Views: 746

Re: Unable to Detect Path to Simulator

So I deleted and reinstalled Prosim v2.30, unfortunately the problem still persists. I have tried to manually direct the path to the simulator, but that still doesn't work.

For reference, I've tried to direct it to C:\Program Files (x86)\Lockheed Martin\Prepar3d v4

I've tried through C:\Users\Name\AppData.....etc.

Basically I've tried every folder that has the name "Prepar3d v4" in it, and none of them will take.

Any other advice would be greatly appreciated.

Edit: I just rolled back to v2.28 again, and it automatically detected the simulator and properly built the database. So the problem seems to be with me and 2.29/2.30.

Matt
by mk882004
13 Aug 2020, 02:24
Forum: ProSimB738 - Technical support - software related
Topic: Unable to Detect Path to Simulator Building Database (RESOLVED)
Replies: 8
Views: 746

Unable to Detect Path to Simulator Building Database (RESOLVED)

UPDATE: I received assistance from Prosim Support. They directed me to the Windows Registry. And to check \\HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3d v4\SetupPath to see if that was directed to the correct spot of my P3D. The path was set up at to C:\Program Files\Lockheed Martin\Prepar3d v4.

My P3d was located in C:\Program Files (x86)\Lockheed Martin...etc. I made that change, and everything is resolved.

Hopefully this can help someone else in the future.

I see that there has been a lot of discussion on this topic lately. However, I can't fix it for myself.

When version 2.29 came out, I had this issue, when I saw that it was a known issue and was being worked on, I rolled back to 2.28 and all worked properly.

I've been busy and sat down for the first time since 2.30 came out, so I installed it, and I have the same issue, it cannot build the database because it cannot detect the path to the simulator.

I once again rolled back to 2.28 and it has no issue. I checked all the file sharing that I know of and made sure that everything was fully shared.

Thanks in advance for your help.
by mk882004
24 Jan 2020, 03:31
Forum: ProSimB738 - Technical support - software related
Topic: CDU Freezes
Replies: 9
Views: 1575

Re: CDU Freezes

I'm thrilled to report that I believe the issue is solved.

I did turn off the ability for Windows to allow my USB ports to be turned off to save power, and I didn't even realize that was an option in Windows until Steve Cos from FDS told me about it. Here is a link to an explanation https://www.hamoperator.com/fusion/fusi ... f-0023.pdf on how to check those settings.

Once I set Windows, I also decided to plug the unit directly into the motherboard USBs instead of on the header. Maybe the power supply through the USB isn't coming through the header properly. (I had tried different USB ports before, but not before I had done the step above), This gave better results, with the CDU buttons continuing to be responsive during the test flight, however, the dimmer knob froze, and neither the keys nor the screen would respond to the dimmer knob.

It got me to thinking that the USB has to be the source of my issues. When I bought my B737 yoke from Agronn, they included in the documentation that they recommended plugging the yoke into a USB hub that has a power supply that was plugged into the wall. If the power wasn't steadily provided it could cause the unit to malfunction.

I didn't think this would be an issue on my CDU because I built a new computer just to run my CDU, I thought the motherboard would be able to provide enough power with only a mouse, keyboard, and the CDU connected to USB ports. So I bought another USB hub with it's own power supply and the CDU worked 100% correctly for over 2 hours. That makes me confident enough to say that I think I found the source of the problem.
by mk882004
24 Jan 2020, 03:30
Forum: Flightdeck Solutions (FDS) / JetMax
Topic: CDU freezes (Resolved)
Replies: 6
Views: 1784

Re: CDU freezes

I'm thrilled to report that I believe the issue is solved.

I did turn off the ability for Windows to allow my USB ports to be turned off to save power, and I didn't even realize that was an option in Windows until Steve told me about it. Here is a link to an explanation https://www.hamoperator.com/fusion/fusi ... f-0023.pdf on how to check those settings.

Once I set Windows, I also decided to plug the unit directly into the motherboard USBs instead of on the header. Maybe the power supply through the USB isn't coming through the header properly. (I had tried different USB ports before, but not before I had done the step above), This gave better results, with the CDU buttons continuing to be responsive during the test flight, however, the dimmer knob froze, and neither the keys nor the screen would respond to the dimmer knob.

It got me to thinking that the USB has to be the source of my issues. When I bought my B737 yoke from Agronn, they included in the documentation that they recommended plugging the yoke into a USB hub that has a power supply that was plugged into the wall. If the power wasn't steadily provided it could cause the unit to malfunction.

I didn't think this would be an issue on my CDU because I built a new computer just to run my CDU, I thought the motherboard would be able to provide enough power with only a mouse, keyboard, and the CDU connected to USB ports. So I bought another USB hub with it's own power supply and the CDU worked 100% correctly for over 2 hours. That makes me confident enough to say that I think I found the source of the problem.

Thanks Steve, Hopefully this can help someone else in the future!

Go to advanced search