

Hitman IF
Members-
Posts
56 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Hitman IF
-
See the sticky: http://forum.lockon.ru/showthread.php?t=8112 Basically install over fresh 1.0
-
Has everyone from lo-mac.com come here?
Hitman IF replied to experimental_pilot's topic in Lock On: Flaming Cliffs 1 & 2
I never liked the Ubi boards due to all the signature banners etc, so I posted on SimHQ instead. I usually post here and at SimHQ. -
Those who got 1.1 at first seem to have got 15, while everyone else seems to be down to 5. I imagine that now the registry activation key saver tool is available, few people will need more than five activations.
-
Seconded. Preferably in the next 1.1 patch rather than wait till 1.2. :icon_pray :dreaming: :icon_pray
-
Ctrl+Backspace will allow you to see your fps in game.
-
More info in a tech preview here: http://www.pcper.com/article.php?aid=140&type=expert&pid=1
-
If you want to see who's the best, simply go to a server on hyperlobby and looks for the guys with the 5:1 or better kill ratios.
-
Thanks Tbird, that's a mostly better font than my attempt at this: http://forum.lockon.ru/showthread.php?t=8539 One thing, I think you're missing Rejoin on Alt+[.
-
Ah, I hadn't thought of that. Thanks for pointing it out GGTharos. Looks like an impossible problem for my mod idea anyway, unless I could get servers to support it.
-
Ok, thanks, that was what I suspected. I'll go away and try to implement something. Perhaps an integrated IFF interogator could be a new feature for a future patch or version of Lock On? It's very difficult trying to engage using the F-15 close combat modes online when the same aircraft types might be on Red and Blue teams.
-
bump. Anyone?
-
I think the widespread use of this kind of physics chip is at least a couple of years in the future. On the other hand, the move to multiple processor cores as a way of improving performance makes it very logical to use a physics processing chip in a similar way to a GPU, particularly in gaming PC's. It would certainly be very useful in a flight sim.
-
Website Suggestion: Virtual Squadron List
Hitman IF replied to Hitman IF's topic in Lock On: Flaming Cliffs 1 & 2
Hi from SVBS Squadron CO: Hitman IF http://svbs.co.uk -- Forums We started out as a F22 ADF/TAW squad for Scotland, but soon grew to be a UK based international squad. We're currently have ADF/TAW, Eurofighter Typhoon and Lock On sections. We recruit all abilities and provide contact facilities (ICQ list & forums), a ladder system and we'll be happy to arrange some training for those who want it. We're quite relaxed about how often you want to play. We don't care which aircraft you fly, so long as you're having fun! -
and use the .bat to start 1.1 afterwards too.
-
I don't think survivability has improved at all. Though I don't think the 3 ejection limit applies anymore with the latest seats. It depends over who's territory you're fighting over I suppose.
-
In all this argument about speed of production of new as opposed to WW2, it's important to note that pilots can't be trained as quickly now, no matter how much money you pour into making rapid production lines for the planes themselves.
-
I suppose that's why the USAF has will have force mix of F-35's as well as F/A-22's. Having something really top notch like the F/A-22 to call on will tip the balance in most fights.
-
Hi, I'm having trouble trying to interpret the "flags" field returned in the LoGetLockedTargetInformation() result table. Perhaps someone here can help me out with a clear explanation. It's specified as follows: flags = , -- field with constants detemining method of the tracking --whTargetRadarView = 0x0002; -- Radar review (BVR) --whTargetEOSView = 0x0004; -- EOS review (BVR) --whTargetRadarLock = 0x0008; -- Radar lock (STT) == whStaticObjectLock (pinpoint) (static objects,buildings lock) --whTargetEOSLock = 0x0010; -- EOS lock (STT) == whWorldObjectLock (pinpoint) (ground units lock) --whTargetRadarTrack = 0x0020; -- Radar lock (TWS) --whTargetEOSTrack = 0x0040; -- Radar lock (TWS) == whImpactPointTrack (pinpoint) (ground point track) --whTargetNetHumanPlane = 0x0200; -- net HumanPlane --whTargetAutoLockOn = 0x0400; -- EasyRadar autolockon --whTargetLockOnJammer = 0x0800; -- HOJ mode I've tested the output to this with different aircraft, with very different results. Note that mig29's and F-15's were jamming. 1 of 2 f5's tws from su27 == 0x20 f5 tws by f15 == 0x80 f5 tws by su27 == 0x20 Mi-26 tws by f15 == 0x808 su27 tws by f15 == 0x80 su27 tws by su27 == 0x20 f15 stt (from tws mode due to jamming) from su27 == 0x10a f15 stt from f15 == 0x800 --don't know what was going on here. f15 stt by su27 == 0xa f5 stt by su27 == 0xa f5 stt by f15 == 0x8 mig29 stt by f15 == 0x108 su27 stt by f15 == 0x8 su27 stt by su27 == 0x10a -- See Note a) f15 eos by su27 == 0x10 su27 eos by su27 == 0x14 f15 hoj by mig29 == 0x802 mig29 hoj by f15 == 0x800 From the values there, you can see evidence of combinations of two or more of the flag constants as per the definition. This indicated to me that the flags field is a 2 byte field with individual bits in that field, or groups of bits, acting as flags. Though I'm not sure where the 0x10* values come from in this scenario, perhaps this was something that was added after the lua script definition was written. Note a) These 0x10* values seem to come when you get a lock against a jamming russian aircraft, so perhaps I added a jamming pod to the su27 loadout by mistake in this case. Could someone from Eagle Dynamics please post a definition saying what each bit (group of bits) flag in the field represents? The info I'm trying to export, is whether or not the radar is on, so that I can make an IFF interogator that only works when the radar is on.
-
Hi all, I was remembering back to the squadron list on lo-mac.com, and wondering if it might be possible for Eagle to post something similar on their lockon.ru site? It could be a good way to get people involved in online flying. Anyone think this is worth doing?
-
Not totally unbelievable, except IRL, the mig won't fly in formation with you for a couple of minutes and give you a chance to escape.
-
Great video. Lots of credit to the camara guy in the -18.
-
I'm getting this too. I can't relate the AWACS calls to the fixes, since I only used them post fix install, but I do think it stutters when the kill messages comes up after the fixes I'm on an AthlonXP 2800+ with 768Mb DDR333 on an MSI KT400A board. Connected at 128/128.
-
Switching from 133 to 400 FSB will give you performance boost, going from 4x to 8x AGP probably won't make much of a difference. Those AGP versions don't have much between them.
-
It doesn't work with tabbed browsing though. The new tab just opens up a new window, which is a little annoying.
-
If you can't afford a new CPU, then you definitely shouldn't be overclocking the one you've got to the point where you can't start the PC. That's asking for trouble. As you will see from the link britgliderpilot gave you, overclocking is usually rather more complicated than sticking on a good heatsink.