Chocolate Software Forums

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1] 2 3 ... 10
 1 
 on: May 20, 2021, 05:06:50 AM 
Started by NET247 - Last post by Russell Gilbert
Hey, that's great!

Glad you found a solution, and thanks for posting it here so other people can find it!

Russell

 2 
 on: May 20, 2021, 04:52:39 AM 
Started by NET247 - Last post by NET247
Solution discovered....

So while they have removed it from the GUI you can manually install the feature.

In command prompt (Run as Administrator) issu the following command:

Code: [Select]
DISM /online /enable-feature /featurename:DirectPlay /all

 3 
 on: May 20, 2021, 04:43:14 AM 
Started by NET247 - Last post by NET247
The problem is there is no DirectPlay available in Windows Server 2019 - I have tried to install older versions of Direct X but with no luck.

It's only frustrating because I've rather enjoyed running a FShost server and tracking flights on it.

If I ever find a work around I'll post it up.

 4 
 on: May 18, 2021, 07:03:53 PM 
Started by NET247 - Last post by Russell Gilbert
Your dxdiag info looks similar to what I have on my Windows 10 PC.

I've looked through my code and checked the files on my PC, and I'm sorry to say I don't think I know the answer to this problem. :-( The fact that it can't initialize FS2002 or FS2004 implies that it can't find DirectPlay on your system. I would suggest doing something like trying to install an old version of DirectX but honestly I don't know how to do that or even if it'll work.

Sorry, I wish I could help more! Please let me know if you find the solution.

Thanks,
Russell

 5 
 on: May 17, 2021, 10:00:05 PM 
Started by NET247 - Last post by NET247
When ever I try start the multiplayer FS Host server (pressing the Play icon) I get the following in red text:  ERROR creating FS2004 and FSX DirectPlay object

My server has DirectX 12 according to DXDiag and all my other game servers run perfectly fine.

I downloaded an ran FSPortTest which passed on all ports.

Yet when I attempted to run FSHost32 with 2002 & 2004/FSX Options selected or just 2004/FSX selected this was the output.

210518 13:57:09  FSHost 3.2 starting
210518 13:57:09  Loaded text messages
210518 13:57:09  Loaded Chat Commands
210518 13:57:09  Remote Access started
210518 13:57:09  ERROR initializing FS2002 DirectPlay
210518 13:57:09  Version check complete. This is the latest version.
210518 13:57:55  ERROR initializing FS2002 DirectPlay
210518 13:58:04  ERROR creating FS2004 and FSX DirectPlay object

Windows Server 2019 has no Legacy Components, and the Add Roles and Features does not have DirectPlay either.

DX Diag reports the following:

------------------
System Information
------------------
      Time of this report: 5/18/2021, 14:00:14
      Operating System: Windows Server 2019 Standard 64-bit (10.0, Build 17763) (17763.rs5_release.180914-1434)
      Language: English (Regional Setting: English)
      System Manufacturer: Xen
      System Model: HVM domU
      BIOS: Revision: 1.221  (type: BIOS)
      Processor: Intel(R) Xeon(R) CPU E3-1245 v5 @ 3.50GHz (4 CPUs), ~3.5GHz
      Memory: 4088MB RAM
      Available OS Memory: 4088MB RAM
      Page File: 3045MB used, 1746MB available
      Windows Dir: C:\Windows
      DirectX Version: DirectX 12
      DX Setup Parameters: Not found
      User DPI Setting: 120 DPI (125 percent)
      System DPI Setting: 96 DPI (100 percent)
      DWM DPI Scaling: Disabled
      Miracast: Not Available
      Microsoft Graphics Hybrid: Not Supported
      DxDiag Version: 10.00.17763.0001 64bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: The file Unknown is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL).  You may be able to get a WHQL logo'd driver from the hardware manufacturer.
      Display Tab 2: Your PC is using the Microsoft Basic Display Adapter. For the best experience, get the latest drivers from Windows Update or from your hardware manufacturer's website. For more information search for 'Microsoft Basic Display Adapter'
        Sound Tab 1: This computer cannot play audio because the Windows Audio service is not enabled.  Use the Sounds and Devices Properties control panel to enable audio. No sound card was found.  If one is expected, you should install a sound driver provided by the hardware manufacturer.
          Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

 6 
 on: May 17, 2021, 06:46:40 AM 
Started by NET247 - Last post by Russell Gilbert
Hi,

I'm not really sure but my understanding is that although DirectPlay is deprecated for new development, it'll still be supported by all versions of DirectX in the future. When I run "dxdiag" on my Windows 10 PC it shows I have DirectX 12 installed, which I believe is the latest. Even though there's no "DirectPlay" tab in dxdiag like there used to be back in DirectX 9, it still works on my PC because the DirectPlay DLLs are included somewhere.

In Windows 10, you can go to Control Panel / "Programs and Features" / "Turn Windows features on or off", and enable "Legacy Components" / "DirectPlay". I have access to a machine running Windows Server 2012 (but not 2019) and when I go to the same window there, it opens "Server Manager" / "Manage" / "Add Roles and Features". There's actually no listing for DirectPlay there but FSHost does run on that machine. When I run dxdiag on that machine it shows that it's running DirectX 11.

Wheat do you see when you run dxdiag?

Thanks,
Russell

 7 
 on: May 17, 2021, 05:02:04 AM 
Started by NET247 - Last post by NET247
Recently I had to upgrade my server to Windows Server 2019 Std Edition.

This has brought about a problem with the lack of Direct Play support.

Is there any known work around to allow running FSHost on Server 2019?

 8 
 on: March 20, 2021, 08:55:57 AM 
Started by ejwells409 - Last post by ejwells409
Does anyone even monitor this site any more (someone who would actually answer a question that is). Anyway, I replaced the Router and Cable Modem with a single integrated modem. Problem solved.

 9 
 on: March 15, 2021, 08:22:18 AM 
Started by ejwells409 - Last post by ejwells409
I am running Win10-64bit/FSX-Accel. Netgear Router (R6220) all ports forwarded and verified "open". Using the current FSHost Client software and selecting "Search IP for Sessions", that button "grays out" and remains that way. . .basically locked up.

 10 
 on: January 26, 2021, 04:22:46 PM 
Started by twotonemurphy - Last post by Russell Gilbert
Hi,

I'm afraid I don't have good news for you. I built FSHost using Microsoft's multiplayer API that they released for Flight Simulator. When FSX was released, they changed to a completely different multiplayer system that wasn't compatible with the old one, so I created FSHostClient to be an interface between FSX and a remote FSHost session on someone else's machine. This works fine, but all of the multiplayer connections are still in FSHost using the original multiplayer API.

The problem is that the original multiplayer API was written using Microsoft's DirectPlay, which is part of DirectX. It was created back in the day when hardly anyone had routers at home, and internet speeds weren't nearly as high as they are now. Plus, graphics cards weren't as fast as they are now, so there wasn't as much data being transferred.

The multiplayer API works by connecting every player in the session DIRECTLY with every other player in the session. FSHost does not relay the data between players - it basically just acts as another player, monitoring everything, but with the ability to control some aspects of what the players can do.

When everyone started getting routers, it became a headache because DirectPlay needs lots of ports to be forwarded in the router. But if it's setup correctly, it works fine for small sessions.

The problem is when you have more than about 15 or 20 players. That's when the amount of data becomes so high between the players that the session starts to become unstable. On top of that, the more people you have in the session, the higher the chances are that at least one of them doesn't have their router configured correctly, which can cause them to be dropped from the session, and sometimes even drop other people as well.

Assuming I'm able to update my programs to work with FS2020, I'll basically just be updating FSHostClient, the interface program between FSX and FSHost. FSX doesn't know anything about FSHost or the multiplayer API, so FSHostClient relays the data back and forth and makes sure each program has what it needs. So I won't really be changing anything in FSHost at all.

VATSIM took a different approach to their server because they knew they could have very large sessions. So instead of using Microsoft's multiplayer API with DirectPlay, they wrote their own protocol to relay the data through the server, not directly between each player. That gave them the ability to drastically slow down the data rate, which keeps the sessions more stable.

So, like I said, I'm afraid it's probably not what you're looking for. The solution would be to write some kind of new multiplayer server in place of FSHost, but you'd still need something like FSHostClient on each person's machine so it could interface between FS2020 (using Microsoft's updated FSX-style API) and the multiplayer server. Then the server could operate more like VATSIM.

However, another problem is Microsoft themselves. They've changed their multiplayer system multiple times over the years, sometimes being completely closed and proprietary, and sometimes creating entirely new systems that had no backwards compatibility with all the programs like mine that were created using their previous APIs. For that reason, I don't know of any other programmers that are working on this issue, and most of the people I did know have long-since given up and moved on to other things. I still maintain my programs and hope to add support for FS2020 but I'm afraid I have no interest in playing cat-and-mouse with Microsoft anymore either, so I won't be re-writing FSHost to work more like VATSIM.

Sorry, hope that at least helps give an understanding of the situation.

Thanks,
Russell

Pages: [1] 2 3 ... 10