Jump to content


  • Posts

  • Joined

  • Last visited

Personal Information

  • Location
    Ottawa, Ontario, Canada, Earth
  • Website
  1. Similar problem here... but only if I fly the Su-33, afterwards the bug applies to everything. http://forum.lockon.ru/showpost.php?p=189151&postcount=59
  2. I am experiencing this same or a similarly frustrating problem. I have a Saitek X45 and I have been using the Rotary 1 on the throttle for the zoom view pretty well since the dawn of LOMAC without error. Now any time I fly the Su-33 things get FUBAR. I can fly any other get in LOMAC 1.12A without trouble, but the moment I fly the Su-33 the joystick axis gets shifted forward... i.e. the neutral position becomes the near fully zoomed position. Rotating back the view will zoom fully out and then zoom partway back in by the time the rotator is moved to the full back position. At all times the view is intolerably spiky. When I quit the game and check the joystick control panel the error is now reflected in the joystick calibration and I generally need to reinstall the stick to fix the error. This problem ONLY occurs after flying the Su-33 in LOMAC 1.12A. I can fly the Su-27 or any other jet to my hearts content without any sign of this bug, so long as I haven't flown the Su-33 beforehand. The moment I fly the Su-33 things are FUBAR until I reinstall the stick or move it to another USB port. I am using the Web version of LOMAC: Flaming Cliffs. I am not using cam2pan or anyother such software. I am using TrackIR and have been since well before 1.1.
  3. Thanks for that worthless reply chennuts. The default connection speed not only causes problems for faster servers and clients, but most new players don't even realize that it causes a problem, or that they have the option of changing it to something much more stable until someone else guides them through it online. The real responsibility is to the developer to either make the the option clearly accessible to the user when he enters a multiplayer game, or to predict appropriately the best speed for that particular user. 33.6 is not an appropriate connection speed for fast connections--it causes stability problems, it's proven--changing your default connection speed involves hunting through furtive submenus and dropping your connection to the server and then starting it back up again. Any sense of responsiblity to be forced through all this rigamarole is lost on the average newbie, they just want to get in the air and shoot some real people. A lot of regulars no doubt forget to reset it on occasion after a reinstall. Changing the default speed should be either obvious to the user, or else it should be something simple for the developers to fix in only one language version of the patch.
  4. You need to review the tone of what you've said. You're just plain rude. You demand charts and referenced research in order to validate an opinion and judge a server worthy of your presence? Get over yourself. :D
  5. Do us a favour and don't play at all. The last thing HL needs is another self-declared expert demanding attention. The servers you find in HL are generally financed by the hosts out of their very own pocket, and are provided to you purely out of generosity. Contrary to what your predictable tone continues to suggest, they don't owe you a thing buddy. ;) Play or don't play, you choose... just save us all from your whining.
  6. Flood mode is a little different. In Flood mode there is no STT, all the launching aircraft's radar energy is simply directed straight forward, and whatever has the tastiest radar reflection within that forward field of view is what the missile will chase after. All SARH missiles compute their own intercept--it would be a lot more difficult for the aircraft to do all the work as it would have to know precisely where the target and the missile is in relation to itself the whole time the missile is in the air. SARH missiles actually only rely on the aircraft's transmitting radar to light up the target and then use those reflections to compute their own intercept. The aircraft doesn't have to do anything other than keep the target illuminated for the missile to find. SARH = Semi-Active Radar Homing, meaning there is a radar dish in the missile seeker cone actively receiving radar reflections, it simply lacks its own radar transmitter. Some modern SARH missiles apparently do use command guidance in the initial stage of a long flight, but they all do their own work for the intercept. Even in this case, I think it would be a simple matter to have more than one in flight at the same time.
  7. And broadcasts your position to everyone on the map. :D
  8. I read your post just fine. As I said, it's a very poor substitute for actually having a true flyable F/A-18C.
  9. It should be fixed. Watching someone do slow predictable laps around an airfield while a Gepard fires a constant stream of tracers way behind him the whole way really irks me.
  10. Sure, you can edit the LUA and fly the 3D frame around, but you're not actually flying a Hornet. It's a very poor substitute for actually having a true flyable F/A-18C.
  11. It's not a mod, that's just the way the AI Hornet looks in LOMAC. It's a shame you can't fly it. :(
  12. It seems to me that the AAA systems in LOMAC should be a little better at aiming than they are. Even the more advanced Gepard and Tunguska have as much a hard a time as the Shilka and Vulcan in hitting anything that isn't in level flight and heading directly away or towards it. Shouldn't these systems be able to compute for beaming targets or targets in subtle predictable banks at very close ranges?
  13. :D http://forum.lockon.ru/showthread.php?t=7885
  14. Holding short and looking both ways is a good way to avoid take-off and landing crashes too. Having an intelligent ATC would be nice, but it isn't that big a deal. IMHO what needs to be implemented the most is line of sight, range, and update limitations to the datalink (and of course no more detecting parked or taxiing aircraft). I think it is silly the way the datalink displays every twitch and turn a contact makes in real-time. The real update period for a EWR datalink would be closer to 10 seconds. I don't know what rate the Russian Mainstay can detect contacts and provide datalink updates, but I'm sure isn't real-time either. I almost never use either in my missions, because it seems kind of arcade-ish as it is now. As far as the NATO datalink not fitting the general LOMAC time period, there are plenty of other aspects of the current game that are too modern to fit the assumed time period (the R-77 Adder for one). Implementing the NATO datalink would compensate for the god-awful AWACS coms logic. One, or both, should be fixed.
  15. I agree that this kind of radar modeling would be time consuming to design, but JF/A-18 pulled it off years ago, and CPUs were quite a bit slower back then. I'm sure many of the real-world limitations of these systems could be modeled well without having to totally redesign the EW theatre.
  • Create New...