ManDay

I.e. same avionics as those of the replaced `plane?

I just asked this because I need someone who can try whether he gets the same problems as me described here. If anyone got a similar system I want to know if he gets similar problems with a (this) joystick.

So this means Lock On is capable of providing other planes than the default-ones? How come - I thought the avionics could not be changed...

What are you talking about?

Which game is this? PS: Indeed, the skinning is horific.

Slt, will you please tell those who never heard of what this is going to be?

What are the so-detailed texture and moddeling on tanks good for if the ground still looks rather average?

Lol, we might make a game out of that: Guessing what the russian threads are about :smartass:

So is that considered "realistic"?

The answer you can find probably here :P

I am using Lomac 1.12a. Kuky, I'll follow your advice. Any Idea where I can get older drivers from? PS: Literally it says "Logitech Force 3D Pro USB9-13-6-1-1668800" under my Input-Settings. And I got finnally contaced by someone involved with EG. I hope this will now bring about the rebound I was hoping for so long. The closer I get to solve this issue the more frustrating it is not to be able to play lomac in MP ;]

***! i formatted everzthing and took the latest drivers and that shit didnt change.

Tried this already. Don't bother. I'm going to do windows a full-over - clean install. first thing after drivers up is lock on being installed. lets see what happens.

Thanks! I think I'll do another Format C: soon. Which OS did you have? Oh and: PS: What did you have written in your settings under Input-Device? In Lockon - where you can choose "Keyboard","mouse" and your joystick i got some weird "Logitech Force 3D Pro USB250760234aGAD12" (not like that but many senseless numbers added to the name)

In fact, programming a interface for HW such as a joystick holds way less possibilities to make mistake than coding a program with netcode, physics, HI, AI etc. This is just an indication that the error is supposedly to search within lockon. As you said: Unlike other games which offer a more arcarde like engine lomac is somewhat sophisticated, Not only an indication but rather evidence for lock-ons fault is that it's the thread causing problems. read my above post - i think that proofs it's lockon's netcode fault. can't force them to help me - either ED accepts it or not. I did everything I can to make it as easy as possible for them to find out - the rest is up to them. Unless I Rev.-Eng. lock-on I wont be able to find the problem within thread 648. There is no "Troubleshooting" as far as I can see. If you got an idea how to approach it I'll follow your instructions €: Oh I see, The ThreadID doesnt really id the thread. Hm. Well: It's the last thread (how else shall i call it) Stack: ntoskrnl.exe!KeWaitForSingleObject+0x4c5 ntoskrnl.exe!KeWaitForSingleObject+0x3f3 ntoskrnl.exe!KeInsertQueueDpc+0x1a3 ntoskrnl.exe!NtWaitForSingleObject+0xbf ntoskrnl.exe!ZwUnloadKey+0x20ad wow64cpu.dll+0x42d9 wow64cpu.dll+0x40e5

Not their fault? It's their thread in their Program causing problems, not the driver of my joystick. What you think?! You think I can go and buy 10 different joysticks just for fun - because ED will not fix their problem? As I said I already tried all that is in my power. I cannot find any more drivers I haven't tried yet. Eagle Dynamics is supposed to support their customers - not just leave it up to the forum-community. PS: I wouldnt have been that pissed if just anyone of ED had donated one single comment or statement in this thread. But as usual (as usual with other companies) the only ones who are commited are the users themselves.

WILL ANY DEVELOPER DARE TO SPEAK UP!? This is the official developer-forum, isn't it?! So will you please help here instead of letting me despair?! Anyway: I found out it's Thread ID 648 causing this problem. Unfortunally, killing or blocking this thread will break up the connection to the server within less than 30 seconds. By the way, I found out that if I don't have my joystick connected, there are at least 2 threads more running than with my joystick connected. Is that something to worry about? The massive amount of context-switching going on in at least 2 of Lock On's threads (among Thread 648 ) is another thing I wonder about.

I really start getting pissed. I tried absolutly everthing that's in my power right now. I even changed my mouse to PS2 and disabled USB2. Nothing... Devs please help me.

http://www.canyouseeme.org/ instead ;)

No probs here. I have some major kind of other problems instead :mad: So, what's the actual problem? Can hyperlobby not etablish a connection - as if there was no internet - or what?

I got the latest drivers. Just d/l them again. For Chipset and Controller Those are all USB 2.0 Ports on only 1 hub Yey, okay. But my BIOS doesnt offer any way to change the latency. Anyway - it's not an issue anymore. =Prophet= I disabled FFB in the Windows-Settings but it didnt help. I found out which Device is causing the problems in the list of devices. Its Human Interface Devices Logitech Force 3D Pro USB (HID) Location 0

I hope this will finally lead to something. I start a new thread since this has now something where to start from. I use a Logitech Force 3D Pro Joystick. If I start the game with the joystick plugged into the USB the game stutters in MP-Games (in MP Games only!). How to solve that? Additional Info (maybe Devs can get something from it): If I plug the Joystick after the game has started, the joystick is not recognized by the game and therefore it's not causing any problems — even tho its recognized by Windows XP!

Oh. This is not good. It's actually the joystick causing problems. As soon as it's plugged into the USB its starting. Don't even have to run up the Joysticks-Controlcenter. Strangely it doesnt stop when I unplug it until I restart the game. I hope you can conclude something from all those points. New Thread created. Please post your suggestions there :>

Ohm na - oh man - awwwwwwww maan. Can you BELIEVE how HAPPY I am getting this fixed?! And it DIDNT stop functioning after the first try (U know I'm used to have such fears as I have experienced that most times fixed things will break up in the next minute). YEEEEEEEEHAW! I'm using a german "Fritz-Box" (avm.de/en) and a Logitech Force3DPro. Currently checking which of those things caused trouble. I immploringly hope it's not my joystick :]

got it. GOT IT! GOT IT! GOT IIIIIIIIIIT!!!! :cry: I'm crying for luck -finnally - after years:smilewink: I can't tell whats the cause yet - but I already eliminated it. It's either my joystick or my WLAN-Drivers. You get a sitrep in half an hour! Thanks for all your help guys!