PDA

View Full Version : What exactly is the problem here?


Pracic
10-30-2007, 02:24 AM
(Originally posted this on the FSInn (MCDU) forums, but was redirected here, sorry!)

Sorry for not being specific with the title, but I am at wits end with FSInn right now.

After getting a new laptop with Vista x64 (I know what you are thinking, and what you want to say about FSInn and Vista x64.. but please hear me out) and a running both FSX and FS9, I found that FSX runs flawlessly, but FS9 has thrown problem after problem after problem at me.

I have solved every single FS9 problem thus far, except one: FSInn.

I have tried EVERYTHING that I could find on this forum, I have followed the entire 70 page manual front to back... TWICE, but still nothing.

I would like to know what EXACTLY the problem is that makes you guys say FSInn is not compatible with FS9 on a x64 system. Why is it not compatible?

The reason I ask is because I can connect and everything is "fine and dandy", only problem is one that has been posted here before, without a solution that works for me. I cannot see other aircraft.

They can see me, but I cannot see them. I assume this is to do with direct play, it turns out that FSInn recognizes the other aircraft, because I can see them on the built in radar, and Servinfo also shows me as online, but flight simulator does not show the aircraft, they are not located in the built in FS chat box, nor anywhere in sight on my scree.
But... they are on the radar, and in PLA.. and anywhere else with FSInn.

So, with Vista x64 running FS9, this is exactly what happens?
If so, I will drop it now and I guess I am screwed. If not, what do I need to do?

I had this problem on my old laptop too, but overnight it magically fixed itself. Not the case this time. Any ideas... anyone? I have done everything short of forcing FSInn to start under Windows XP SP2 or things like that.

Included in what I HAVE tried:
Closeing Anti-virus/firewall
Disabling UAC
Disabling Windows Defender
Complete uninstall of all antivirus (including using Norton remover tool)
Completely disabling EVERY anti-virus, firewall, and system protection utility available
Disabling upnp
+All of the above in combination
Both FSInn 1.2 and 1.3 (and FSCopilot 1.6/1.7, respectively).

A few other things that I found with FSInn:
1. It will not connect automatically, if I click the orange button to make it connect me to the FSInn host, it will not. I have to connect manually via the built in Flight Simulator multiplayer window. This is not a big deal, so I don't really care, but I thought it might help if I mentioned it
2. When connected, every aircraft that is near me, and shown in the "PLA" window, has the arrow shown, but it blinks between gray and blue. Doesn't matter if I double click/click/right click, it always stays the same.

Funny thing though... the exact same thing happens with Squawkbox. Doesnt matter what I do, but I can never see anyone else. Heck, even ATC can see me and talk to me (and I can talk back), but I cannot see the other aircraft.
Another thing that confuses me: if this is a problem with DirectPlay or the likes, then why is it possible for me to connect naturally through the built in Flight Simulator multiplayer? I can connect to someone else's game and we see eachother and can play and fly as if it is in "Turbo mode" in FSInn, getting perfect performance and updates of eachother.

Now, if you tell me that this is exactly the problem with running FS9 on a Vista 64 system, then I regret not being able to play FS anymore. Sure I can go to FSX, but thats A LOT of lost addons...

It'd be nice if I could, at the very least, connect via SB3 (I know, I hate saying that, FSInn is way better, IMO), but I can't even do that.

I'm sincerely sorry for posting this if there really ARE solutions elsewhere, but I am not lying when I say I have searched this forum like never before, and I have read the manual ten times over, and followed it step by step making every change at least twice.

Which leads me to think that this must in some way just be a stupid little thing that I missed. Any ideas?

What I haven't tried is clicking the three green little squares or whatever that pop up in the control panel when connected. I read that clicking them to make them red will make other aircraft invisible. I was going to try clicking it to make it red, then going back to green, but I keep forgetting. Would that work? Is it worth a try?

Finally, I would like to ask why it isn't possible to simply have FSInn run in 34 bit mode. I mean, I have so many other programs that do it, so if 64 bit processes are precisely the problem, why can't this be done for FSInn as well?

I am sure there will be people who link me to other threads and the like, and I have more than likely already read them through more than once. But I still urge you to post as many links and support sites as you can, with the idea that I might have missed one!

Anyway, for those that can give input, I value your response(s) greatly! I have honestly never been so stumped before, normally I can solve my own problems without even having to look at a manual, but this time I have done it all. Thank you very much for your time and help!

Update:
-------------------
Okay, so I know its definitely not the fact that "FSInn is not compatible with FS9 on a Vista x64 system", because there are a handful of guys on SB3 that managed to get both FSInn and squawkbox working on both Vista 32 and Vista 64 systems. I tried everything they had in mind but it still won't work for me.

Looks like someone obviously wants me to give up. Well, that ain't gonna happen!
-------------------

Thanks for any and all help!!!

L. D. James
10-30-2007, 02:50 AM
Hi, Pracic. It would have been nice to have a more descriptive title. It'd make the forum as a searchable database easier for others with similar issues to find resolutions. Also, you have quite a few issues in the same topic. Of course, I understand your being anxious.

I'm not sure whether to start out with addressing the issue with FSX or the issue with FS9. Also, working with a 64bit system, I'll kind of have to rely on your execution of the steps and feedback on how it works. So far I've had success, but since I don't have a 64bit OS I can't test it as I have with the 32bit versions of Windows XP and Windows Vista.

When you reply, please indicate which OS we'll be working with first. Start out by right clicking on the fsx.exe (or the fs9.exe) file. Go into properties and set the compatible mode to "Run as administrator". It doesn't matter whether you have UAC turned on or off.

Check and insure that you don't have the observer's option selected in the Inn Control Panel under Set -> General -> Basic.

Let me know if this cures the problem with you being seen by ATC and the other pilots.

-- L. James

--
L. D. James
ljames@apollo3.com
www.apollo3.com/~ljames

Pracic
10-30-2007, 03:43 AM
Sorry about the topic title and not being so descriptive.
I finally found a solution though!

But first, just to be more descriptive:

FSX was running fine, I never had any problems with it whatsoever, nor FSInn running with FSX.

FS9 was the sim with the problem, when running it with FSInn (or squawkbox for that matter), I could connect properly but I would not be able to see any other aircraft, even though they could see me.

I am running Vista Ultimate 64bit. This is the OS that made FS9 have problems. When running on XP Pro (Sp2) I never had any problems, but running on Vista Ultimate 32bit, I never had any problems.

So, in summary - the problem was between FS9 (FSInn) and Vista Ultimate 64bit.

The cause of the problem turned out to be Norton Antivirus. I THOUGHT I had removed it completely (even used a special removal tool), but there were still minor traces left. After finally going and removing everything Norton Internet Security-related, FSInn started showing all other aircraft.

I hope this helps those who may encounter this issue, because I honestly spent the past week, about 5-8 hours a day tearing out my own hair now knowing why it wouldn't work.

Thank you Mr. L. James for your help, and I sincerely apologize for any problems caused when posting this on the MCDU forums, and for topic title/description being a bit vague.

I am very happy to have this working out, but even happier to not have to resort to using SB3, rather, I can fly online with FSInn again!

Thank you very much for everything!


(As a sidenote, just so anyone else knows, after uninstalling Norton Anti-virus (COMPLETELY) I was able to turn on other anti virus and firewall programs including AVG, Windows Firewall/Windows Defender, and the UAC, and still had 100% good connection with FSInn).

L. D. James
10-30-2007, 03:50 AM
Thanks for the acknowledgment that it's working. So far a verification of the steps (which includes check the Firewall/Antivirus program) has been a cure-all.

Happy flying.

-- L. James

--
L. D. James
ljames@apollo3.com
www.apollo3.com/~ljames