ForumJet45 AAS Support: Jet45 AAS SupportJet45 Suite Goes Blank

Please or Register to create posts and topics.

Jet45 Suite Goes Blank

#1 · September 23, 2018, 9:49 pm

Hey Guys,

I know some of you have been having some issues with the Jet45 suite components dealing with the graphics and the network. I'm having an issue and have been trying to resolve it now for a while. Just to give you a little background on my problem, whenever I load any of the components (MFD.PFD, RMU, etc...), it loads perfectly in it's respective window. Whenever I load the Wide Client, it connects with FSX and the instruments use to load values, but after about 2-5 minutes, the components would start flickering, and eventually would shutdown. I've taken several steps in trying to resolve that issue. I have 2 Nvidia Geforce graphic cards, one is a 630 and the other is a 440. I'm utilizing the 2 VGA ports and the 2 DVI ports, but since the MIP monitors are all VGA, I have one down converted to VGA via a DVI-VGA adapter. As long as I don't initiate FSX FSUIPC, the components run fine. As soon as I bring up FSX and Wide Client connects, it blanks out the components and I can't see any of my data.

Steps taken to try to resolve issue...

removed graphic drivers and reinstalled
Ran Wide Client in "Above Normal Mode"
upgraded my switch/router to Gigabit
disabled the firewall

The ASI, ADI, and the Altimeter components from another third party doesn't blank out, It just starts flickering after 2-5 minutes of Wide Client running. Have any of you guys experience this problem?

#2 · September 24, 2018, 5:32 am

Hi Bryant,

Strange happenings at your place. I have had problems in the past but not yours. I have had the one screen go blank but that was because the VGA went bad, so I had at least the option to go to DVI.

In your case all the screens are going and the common link is Wideclient. Therefore I assume you are running the FSUIPC version for FSX and not for P3D v4.3 ? If I remember you should be on version 4 of FSUIPC not 5 which is for the 64bit version. By extension is your version of Wide client the correct one ?

If you go to Pete Dowson's forum you may find others with a version mismatch problem.

Just confirm that you are running the correct version and we'll continue from there.

Mark

#3 · September 24, 2018, 11:22 am

`Hey Mark,

That's one of the things that crossed my mind. I did check out Pete's forum to see if I could find anything on this issue, unfortunately not this specific issue. You mentioned that FSUIPC4 is for FSX and FSUIPC5 is for P3d, 64bit. Are you aware whether or not if FSUIPC4 is also a 64bit app? I know my windows 10 is a 64 bit operating system.

#4 · September 24, 2018, 8:14 pm

Hey Bryant,

This is something several of us have seen including myself. The data on the MFDs start going crazy and haywire, is that correct? If so, I believe it is a networking issue between your server computer and your client where your Jet45 components are running. It's a bottle neck of information issue.

I don't think it has anything to do with whether your using DVI or VGA to connect your monitors. I am running all VGA as most of us are because we are stuck needing 15" standard monitors.

Are running all of your Jet45 components on one Client machine? If so, you may have to break them up on two machines. In other words, you will have three computers running, one Server and two clients. I did this and as best as I can remember, most if not all of my issues went away.

Check out these threads out real quick:

Jet45 AAS Stutters and Erratic Behaviors

PFD and MFD Crashes on Two PCs

#5 · September 24, 2018, 10:05 pm

Hey Ron,

Yes, the data goes haywire whenever Wide Client connects to FSUIPC. I figure it has something to do with my network, also I see that it requires net frame 3.5.1 to be running on the client, I'm not sure if this is required in Windows 10 or not. I'll check on that as well. Jet45 is running on a high powered quad core gaming PC with 16 GB of ram. I have another PC I could use to take some of the graphics load off of it, but I would this this high powered PC would be capable of run all three monitors. Actually I failed to mention that I have a KVM switch between the Client and the server, this is the easiest way I know how to administrate between the client and the server. Does anyone else use a KVM switch?

#6 · September 25, 2018, 6:25 am

Quote from Mark Speechley on September 25, 2018, 6:25 am
Bryant,

I re-read your post again after Ron's reply. I have had the data go crazy but not to my memory a shutdown or blanking of the screen.

I did have that problem resurface again a few months ago, but not since. I had too many programs open was the problem.

There are a few fixes for your Jet45 problem over the years, but most have not been successful for me. The only way I got on top of the problem was as Ron pointed out, spread Jet 45 over multiple computers. In my case I have 4 computers to run everything.

1/ P3D v4.3 Graphics Server Win7

2/ Win7 PFD1,EICAS

3/ Win10 MFD, PFD2, FMS

4/ Win7 RMU, Gauges

If you are bored you can revisit Pete Dowsons forum and look for a post from Allan (English Rebel) discussing this exact problem. The executive summary was it was most likely a software that needed more codework and was not his Wide client/server.

If you want to fry your brains you can read, I think in the advanced pdf notes, for FSUIPC, which comes with the program. In it you can find out about Wideclient log which will show you the traffic running through that particular computers wideclient. You will see very quickly that one parameter should be in the low numbers e.g 10 but with Jet45 running you can be in the hundreds ! That is the reason for the overload you are seeing. Throw in other back ground programs that may access FSX through Wideclient and you have a bigger recipe for disaster. That is why THE recommendation is to spread over more computers. You can try other recommendations like memory managers that have worked for some, but didn't in my case.

Your on board graphics RAM amount is essentially irrelevant, for a 32 bit program. FSX and P3D v1-3 is 32 bit and can only use up to 4Gb maximum. It does not matter if you have 16Gb ram, FSX can only use essentially up to 4. The more programs the less room for everything to run. For FSX you can only run FSUIPC ver4. Your Net Framework should be OK as it usually updates in Win10. If not you can look for it on the microsoft website.

I too have a KVM switch for two of the computers to share a windows monitor. No dramas at all.

Summary, (in my situation)

You will need a minimum of 3, preferably 4 computers. Your big gun computer is only needed for the Graphic screens and FSX/P3D. You should be able to get away with smaller/older computers for the Jet45 components.

2. FSX is 32 bit and is limited by 4 Gb RAM. P3D v4 is 64 bit and most advice is 16 to 32 Gb is recommended. Whichever you have can determine which version of FSUIPC you will require. Give some serious thought to updating to P3D. Ver 4.3 is working like a charm for me. I don't think V5 will be out till late next year.

3. Check out your Wide client log and all may be revealed.

Cheers.

Mark S.

Bryant,

I re-read your post again after Ron's reply. I have had the data go crazy but not to my memory a shutdown or blanking of the screen.

I did have that problem resurface again a few months ago, but not since. I had too many programs open was the problem.

There are a few fixes for your Jet45 problem over the years, but most have not been successful for me. The only way I got on top of the problem was as Ron pointed out, spread Jet 45 over multiple computers. In my case I have 4 computers to run everything.

1/ P3D v4.3 Graphics Server Win7

2/ Win7 PFD1,EICAS

3/ Win10 MFD, PFD2, FMS

4/ Win7 RMU, Gauges

If you are bored you can revisit Pete Dowsons forum and look for a post from Allan (English Rebel) discussing this exact problem. The executive summary was it was most likely a software that needed more codework and was not his Wide client/server.

If you want to fry your brains you can read, I think in the advanced pdf notes, for FSUIPC, which comes with the program. In it you can find out about Wideclient log which will show you the traffic running through that particular computers wideclient. You will see very quickly that one parameter should be in the low numbers e.g 10 but with Jet45 running you can be in the hundreds ! That is the reason for the overload you are seeing. Throw in other back ground programs that may access FSX through Wideclient and you have a bigger recipe for disaster. That is why THE recommendation is to spread over more computers. You can try other recommendations like memory managers that have worked for some, but didn't in my case.

Your on board graphics RAM amount is essentially irrelevant, for a 32 bit program. FSX and P3D v1-3 is 32 bit and can only use up to 4Gb maximum. It does not matter if you have 16Gb ram, FSX can only use essentially up to 4. The more programs the less room for everything to run. For FSX you can only run FSUIPC ver4. Your Net Framework should be OK as it usually updates in Win10. If not you can look for it on the microsoft website.

I too have a KVM switch for two of the computers to share a windows monitor. No dramas at all.

Summary, (in my situation)

You will need a minimum of 3, preferably 4 computers. Your big gun computer is only needed for the Graphic screens and FSX/P3D. You should be able to get away with smaller/older computers for the Jet45 components.

2. FSX is 32 bit and is limited by 4 Gb RAM. P3D v4 is 64 bit and most advice is 16 to 32 Gb is recommended. Whichever you have can determine which version of FSUIPC you will require. Give some serious thought to updating to P3D. Ver 4.3 is working like a charm for me. I don't think V5 will be out till late next year.

3. Check out your Wide client log and all may be revealed.

Cheers.

Mark S.

#7 · September 25, 2018, 8:46 pm

Quote from Ron Rollo on September 25, 2018, 8:46 pm
Hey Bryant,

I think we are getting to the root cause of your issue. You need to spread the Jet45 AAS load on to two Client computers. (Your Server computer is running the flight sim and main graphics) For the record, having the baddest, fastest and newest computer is great and will run all the elements of Jet45 with no issues. The problem is getting the information from one computer to the other over the network. It is a bottle neck issue. Once you spread that load over two client machines, you will see that everything will run smooth. Instead of on highway between two computers, you will have two highways between three computers reducing the traffic by at least half.

Eric Tomlin was running his FS9 flight sim on four really old and slow computers. The computers were slow but because the Jet45 AAS load was spread over THREE client computers, his avionics were smooth as silk.

In the beginning, I was able to fine tune my two computers and get Jet45 to run without too many issues. But it is a balancing act. You have to be really careful what programs you are running and how much information is being shared between the computers. Eventually I went to three computers and problem solved.

Right now as you know my sim is down. I plan to rebuild my computers using close to the top of the line i7 processors, solid state drives, lots of ram and high end graphics cards. With that said, from what we have learned over the past several years is that this is going to be a waste of good money. However, spending good money on high end hardware for your Server PC where your flight simulation and main graphics is being calculated is a must. The other computers can be scaled down.

The main reason I am going high end on all of my computers is to rule out once and for all that the issues we have been seeing has anything to do with scaled down computers. So the bottom line is even with two of the best computers you can buy, you will be subject to the Jet45 data going haywire if all you are running is two computers.

One other quick question. You mentioned that your are running FSX Steam Edition. Have you thought about switching to P3D Version 4.2? It is a 64 bit flight simulator and the best on the market.

Hey Bryant,

I think we are getting to the root cause of your issue. You need to spread the Jet45 AAS load on to two Client computers. (Your Server computer is running the flight sim and main graphics) For the record, having the baddest, fastest and newest computer is great and will run all the elements of Jet45 with no issues. The problem is getting the information from one computer to the other over the network. It is a bottle neck issue. Once you spread that load over two client machines, you will see that everything will run smooth. Instead of on highway between two computers, you will have two highways between three computers reducing the traffic by at least half.

Eric Tomlin was running his FS9 flight sim on four really old and slow computers. The computers were slow but because the Jet45 AAS load was spread over THREE client computers, his avionics were smooth as silk.

In the beginning, I was able to fine tune my two computers and get Jet45 to run without too many issues. But it is a balancing act. You have to be really careful what programs you are running and how much information is being shared between the computers. Eventually I went to three computers and problem solved.

Right now as you know my sim is down. I plan to rebuild my computers using close to the top of the line i7 processors, solid state drives, lots of ram and high end graphics cards. With that said, from what we have learned over the past several years is that this is going to be a waste of good money. However, spending good money on high end hardware for your Server PC where your flight simulation and main graphics is being calculated is a must. The other computers can be scaled down.

The main reason I am going high end on all of my computers is to rule out once and for all that the issues we have been seeing has anything to do with scaled down computers. So the bottom line is even with two of the best computers you can buy, you will be subject to the Jet45 data going haywire if all you are running is two computers.

One other quick question. You mentioned that your are running FSX Steam Edition. Have you thought about switching to P3D Version 4.2? It is a 64 bit flight simulator and the best on the market.

Meta

HANGAR 45 FORUM

Jet45 Suite Goes Blank