Back to Board Index
Back to Board Index
Forum help
| Windows 8 is running FSOpen Server2 successfully | |
Robert Dunn  24th Feb 2013 11:01:52 | Our installation of FSX host running on Windows 8, 64 bit OS has been running almost flawlessly for the last three weeks. The FSOpen Server2 installation worked on the first attempt. We installed WinPCap in compatibility mode as advised and documented on this forum. We exexuted the FSOpen Server2 installation in compatability mode, as the Windows 8 installer dialog box required. We run Pro (payware) version of FSOpen Server2. Our FSX multiplayer host program installation is modified only with the "Bojote' Tweaks", virgin and otherwise unenhanced, all relevant settings sliders to the left, other options minimal and in Tower role. We disable in-game voice totally and do not (yet) use FSOpen Server2 TeamSpeak-FSX radio features. Our voice commo is via TeamSpeak3 totally. Our FSX host server is an i7 Intel CPU, Nvidea 1 Gb GPU, 8 Gb moderately fast RAM, 256Gb moderately fast solid state drive. Our FSX host server is always on line, always moderately busy, occasionally serves 25 to 30 FSX multiplayer clients on a residential cable plan (ComCast USA) spec'ed at 6 Mb/s upload and 50 Mb/s down.
Are any of you other FSOpen customers running FSOpen Server2 on Windows 8 ? If so, what is your experience with this software/operating system combination? How long have you been running a Windows 8 FSX host? Very rarely (once or twice a week on a 24/7/365 FSX host server) FSOpen Server2 window will grey out and desplay an error condition dialog box "FSOpen has stopped responding". In this error state, no further cursor or keyboard inputs are accepted, else the program logically closes. HOWEVER, even in this error state, FSOpen Server2 continues to perform ALL its normal functions, reporting packet flow, injecting bot text, executing "!" commands, feeding data to FSOpen map, FSOpen Pilot List and FSOpen/sessions, etc. Additionally, FSOpen/sessions no longer displays the real world weather cloud icon at the left of our session line. This icon always displayed correctly when we previously ran FSOpen Server2 on Windows 7 64 bit. We continually select "real world weather-15 minute injected" when initiating FSX multiplayer host server, and weather functions in-game normally. The cloud icon in FSOpen/sessions is inconsequential to our operation of our FSX host and no action is being requested by us. Cloud icon observation is purely for your general information, Mr. Wave. Respects, Bob... RSDunn@msflights.net email msflights.jmainguy.com TeamSpeak3, I'm "always" logged on |
David Figge   24th Feb 2013 11:54:25 | Robert
RealFsx server has Windows 7 64-bit running the pro version of FSopen Server2. We are experiencing the same so I don't think it's related to Windows 8. Noticed it for the first time a few weeks ago. It's possible a window's update has effected the FSopen Server Best regards |
Dave Wave  24th Feb 2013 11:57:45 | Can you guys keep a note of when this happens please.
|
| Robert Dunn 24th Feb 2013 13:32:51 | I will comply, Mr. Wave. I'll capture what information I can anecdotally and capture the event viewer log as best as I can. We reboot our server to change FSX host airports or to clear other FSX or FSOpen errors daily and, as our FSX host is usually in constant solo operation, reboots and resettings are done as rapidly as possible (5 minutes). I emphasize that FSOpen continues to operate normally in this error state. It just can not have any settings changed when "not responding". The inconvenience to our FSX host operation is very minimal.
Mr. Figge; I appreciate very much your information. The onset of this "not responding" error condition seemed to correlate with our host OS upgrade from Win 7 to Win 8. I now know that there probably is not such correlation. Separately, Mr Wave; I note and admire your customer support here in forums as well as overall. I read of your unsolicited offer of cost refund to a customer here in forums who had misunderstood the nature of one of your products. You, sir, and your company are indeed a class act. We at msFLIGHTS.net have recently had several FSX third party content developers drop by our TeamSpeak for the purpose of unstructured FSX multiplayer specific conversations with our then present members. These welcome visits have been unannounced, spontaneous conversations on many topics relevant to the general FSX multiplayer community. These conversations have been informative (both directions), sparkling and usually lengthy. I would respectfully invite you to drop in to our TeamSpeak or post on our forum any time you would like for any purpose that might suit you. We'd love to talk with you. Respects, Bob... |
| Robert Dunn 7th Mar 2013 03:36:07 | Since my original documentation on the "not responding" error state, I have had only one instance of this occurring, happening upon initial FSX host installation over an already successfully running FSOpen Server2 in a waiting state. A simple software reboot quickly and permanently resolved this error. Therefore, I am going to consider this very occasional situation a non-problem and discontinue my monitoring of it. In our Windows 8-FSOpen installation, the real world weather icon, which used to appear in Windows 7 and should still display, still does not appear in FSOpen/sessions listing. As I said before, this lack of a black raining cloud real world weather icon is of no concern to our efficient FSX host-FSOpen Server2 operation and is FYI only.
Seperately, the 5 minute upper limit on the bot text injection continues to be the biggest hinderance to the smooth operation of our FSX host-FSOpen Server2 implementation. The injected text interrupts the textual chat use of the FSX Briefing Room Chat by our non-TeamSpeak using pilots. We do not implement in-game voice at all, relying totally on TeamSpeak3. The copy and paste nature of the FSOpen functioning makes other operation and textual use of our DEDICATED server cumbersome and fought with thusly induced error. Because we rely on the "!" commands frequently, turning the bot off at FSOpen boot up is no solution at all to our problem. Increase of the bot autopost time limit to some value north of 15 minutes would greatly alleviate our frustrations with an otherwise useful and well thought out software, for which we pay a subscription fee. Respects, Bob... RSDunn2@msflights.net msflights.jmainguy.com TS3 |
Sarvesh Patel  10th Mar 2013 01:41:25 | Can u tell when it happens |
You need to Log on to post a reply. |
Forum help