Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
Entirely possible your buddie is blocking the connection, unknowlingly.
This is a good question. Was just about to ask it.
Originally posted by mikeytwc:
I just re-read your reply about 5 times, and I think i understand the issue now YOu have replaced the gamespy coding with STEAM, which does not allow for direct IP connections, is that correct,(that STEAM does not allow for direct IP connectins to software running on its platform?) or am i over-simplifying it
DTG_Admin:
The Steam multiplayer system does allow LAN play Mikey. It does not allow for Direct IP multiplayer however. All FSX multiplayer features require you to be logged into and running Steam. This was not a design choice but rather it the way the Steam system functions. Our focus was on providing players with a replacement for the discontinued GameSpy service and the Steam multiplayer functions were the obvious choice for this.
- Martin
hi again Martin, thank you for the clarification, I believe I now understand the concept of why the ip doesnt work, hopefully that can be resolved at a later date, I really do appreciate all you at DTG have done to provide us with a stable MP platform....
mikeytwc
Ya so basically forcing the users of the boxed version of FSX to buy the FSX:SE to play online with FSX:SE users, However not really a bad thing.
As I said before I will not be switching over to FSX:SE until the PMDG 737 NGX works. Once the PMDG works then, ya I might buy it because I watched a video about doing an ultimate stress test with FSX:SE, and if you try the same test with the FSX boxed, the boxed set would crash. ---> Video: https://www.youtube.com/watch?v=4YONKVA8c00 <---
Once my Virtual Airline supports FSX:SE (if they do) I I might even permanently switch the FSX:SE.
I do however wish that dovetail approached the FSX community on the AVSIM forums and other FSX forums before the release of FSX:SE, and ask the communtiy what add-ons we used so the add-ons would be compatible when the game got released on steam. There was a thread on the AVSIM forum about DT getting the FSX license and I didn't see one post from a representative from DT at all.
The Steam multiplayer system does allow LAN play Mikey. It does not allow for Direct IP multiplayer however. All FSX multiplayer features require you to be logged into and running Steam. This was not a design choice but rather it the way the Steam system functions. Our focus was on providing players with a replacement for the discontinued GameSpy service and the Steam multiplayer functions were the obvious choice for this.
DTG Admin has also said finding a way so you don't have to be logged into and running Steam to run FSX-SE is on their to-do list. I'd like to ask DTG Admin if once that is accomplished, would they consider re-enabling the multiplayer direct connect capability? The lack of this capability is "preventing" a lot of FSX users from switching to FSX-SE.
Thanks,
Al
I'm not looking to start a fight here but I want to voice my opinion on this, I personally think the ONLY thing preventing FSX users from switching (especially the players with Virtual Airlines and countless add-ons) to FSX:SE is the lack of add-on compatibility from the boxed version that most users use. Once I flew the PMDG 737 NGX there was no going back for me, PMDG puts alot of time and effort into their products to make your flying more realistic, and other PMDG users probably feel the same way. The users of the boxed version of FSX are just so used to add-ons we don't really want to go back to default aircraft and default FSX.
The direct connect feature getting re-enabled would only allow the FSX boxed users and FSX:SE users to be able to play on the same server because the boxed users use the direct connect feature to connect to the FSOpen servers.
I'm not looking to start a fight here but I want to voice my opinion on this, I personally think the ONLY thing preventing FSX users from switching (especially the players with Virtual Airlines and countless add-ons) to FSX:SE is the lack of add-on compatibility from the boxed version that most users use. Once I flew the PMDG 737 NGX there was no going back for me, PMDG puts alot of time and effort into their products to make your flying more realistic, and other PMDG users probably feel the same way. The users of the boxed version of FSX are just so used to add-ons we don't really want to go back to default aircraft and default FSX.
The problem of third party addons is, and will, go away with time. PMDG has just announced an FSX-SE installer for the T7 and installers for their other planes, like the 737NGX, will follow shortly. All the major third party developers are working to get their products FSX-SE compatible. If nothing else, they want access to the growing FSX-SE market.
Al
Not sure why you cannot connect on Steam but it may have something to do with having Steam loaded first (which uses the default directories that otherwise the box version of FSX would use). Try uninstalling both, the load the box version first followed by the Steam version.
You can also connect either the box version or the Steam version (running in Free Flight) to servers like FSCloud - http://fscloud.net/fsclouddownload2.php You will need to be sure you have netframework 4.5 or higher (the easy way to find out is by downloading it from Microsoft and installing it - https://www.microsoft.com/en-US/download/details.aspx?id=42642 ) although if you Google how to know what netframework version you have you will find how to see your current version.