Tallyho1961

The patch is very much appreciated - especially repairs to F-15 HUD Nav Block and whiskey compass! Outstanding product overall!

I'm always relieved to find out it's not my system/installation. I've done a fair bit of adding-on, tweaking, etc., lately and feared I might have upset something.

Sometimes - it seems when flying over very uneven terrain - the F-15 altitude tape (HUD right side) get totally jerky (slideshow like) and even out of synch with the altimeter. Is this modelling RL behaviour over mountainous terrain or, am I looking at something else?

I gotta say I find this stuff fascinating. I'm going to print the contents of this thread and test the various points you've all raised. As it is, I'm not experienced enough in e-warfare to keep up with what's being posted. Great discussion. I'm actually hoping it continues :)

Thank you, gentlemen - I'll do some familiarization with your advice tonight. It's stated above that with the EOS off, I'll no longer receive IFF information. I'm still new to jetsims, so I'm a bit lost here. A couple of quick questions, therefore: 1. What does the EOS system do for me? 2. What constitutes IFF information in LOMAC? 3. Is EOS on by default? 4. Why would I turn it off? Cheers, Dave.

The keycommand list includes one for toggling the electro-Optical system in the Su-27/33 and MiG-29, but when I activate it nothing seems to happen. Anybody know anything about this? While I'm on the line, does the MiG have ECM capability? Again, I can't see a confirmation light when I activate. Thanks in advance!

I was about to post my own question about cockpit illumination, so rather then start another thread, I thought I'd add to your question: What is/are the correct colour(s) for cockpit lights in the aircraft represented in LOMAC? I assume the mods were made because the default orange is not realistic.

Excellent news! Thanks for the update.

AFAIK, the final leg always point straight to the airfield. An offset to the IAF makes very good sense and would be a fine piece of programming. Thanks for that one!

Let me know. I'll co-sign.

Am I the only one who wasn't copied on the memo? :cool:

Roger that. Thanks for your time!

I like this modern flight combat world - there's lots to learn. I was a big jet nut back in my early teen years. I built models of the F-105, F-22, F-111, Mig-15, Mig-21 and others, then completely forgot about the whole thing for like 30 years. What I like about LOMAC, like IL2's WWII world, is that it's re-connected me with all this stuff. The reason I bought LOMAC/FC is that I attended an airshow about six weeks ago to see the WWII a/c: P-51, Spitfire, B-25 and B-17. Then an F-18 did a flypast and a few flashy manouevers and I figured I should try a jetsim out. Glad I did - it's great fun. PS - For what it's worth, this is the line on missile flight from the 1.1 ReadMe: 'Rockets and missiles now rotate around their longitudinal axis when in flight.' Do they mean A2G missiles? Because the Mavericks don't rotate either.

Hi Krusty, Ya know, I had noticed the steering bug error, but it was getting late and I began to weaken :icon_jook The more I think about it, it would be nice if the F-15 navigation bugs could be addressed. I've learned to love complex flight sims (two years with IL2) and I'm a full-out immersion nut. Aside: For my radio commands in LOMAC I use a voice recognition program and figured out how to disable both the audio repeat of the command I issue and the on-screen text message that accompanies it - you just rename a pair of folders. I love speaking a command and hearing a response without any visual backup. It really feels real. Sometimes the message can be hard to hear - but I'm sure it sometimes is in R/L :cool: Anyway, because these F-15 bugs are very visible, and learning to interpret the HUD is a big part of flying a modern combat jet, seeing them hurts immersion. Sure, they can be ignored and worked around, but wouldn't it be nice... Hi GGTharos, When you mention the A2A missiles, is the problem that they don't spin when in flight (the Hydra-70s do) as announced in the 1.1 ReadMe? I noticed that because I like to use chase weapon view from time-to-time.

Roger that. I hadn't noticed the combat mode/HSI bug - you've saved me another thread :) I'll keep my fingers crossed that some F-15 lover will convince them to fix these issues. I figure if you're 90% of the way there, finish the job right. But that's me. Thanks for clearing this up for me, I'm off to learn more about using my A2A missiles. Even if I get lost doing it.

Hi, It's great to hear from somebody on the Dev Team :) 1. Understood - I thought I might have a corrupt installation. 2. Does this mean the HSI is inaccurate in ILS mode? 3. Good news - saw this in another thread. Are these issues slated for repair in the 1.2 add-on I've been reading about? Thank you. Dave. PS - Love your product.

Caveat: I'm normally not this anal, but this is such a fantastic sim, and errors are immersion killers, so here goes: I started by writing down the waypoint headings and distances so I could cross-check the various instruments along the way. On this particular mission, although I will try others, it is mostly the NAV block that is fouled up. Observations: 1. The HSI gave course/time-to-waypoint indications that were as per the mission briefing 4 out of 5 times. On the final leg, the mission briefing gave a heading of 86 degrees, while the HSI brought me in at 99. It didn't really matter because I could see the airfield at that point, but it was an error nonetheless. 2. The NAV block readings agreed with the HSI and mission briefing only on the first leg. After that, the NAV block was fouled up all the way along and in different ways each leg. It would give distances like 1.4nm when it should have been giving, like, 36nm. Then, on one leg, it seemed to catch up with the HSI all of a sudden. On the last leg it was just behind the HSI and, like I said, it didn't matter because I was about to make a VFR landing anyway. 3. The heading tape waypoint index can also be off the HSI/mission briefing by a couple of degrees. It doesn't really matter but you would assume it would agree with the other settings. The problem with the NAV block being fouled up is that it the most convenient way to keep track of where you are. You can keep dipping your head to check the HSI, but who wants to do that. I've only been with LOMAC for about a month and until a few days ago was flying only the A-10 to help me learn the ropes. I didn't notice any errors on its NAV block/HSI/HUD/compass readouts, and I assume this sort of thing is part of 'core code' as opposed to aircraft-specific stuff, so I find it odd that the F-15 is out of whack. Anyway, I'd love to know if I'm the only one who's noticed this.

Hi, I'm testing this right now in one of Thomas Weiss' missions and it look like a couple of things are askew. For NAV info on the F-15 we've got five sources: 1. The HSI and its course/distance-to-next-waypoint indicators. 2. The HUD heading tape 3. The HUD heading steering index and assigned heading indicators 4. The canopy frame-mounted compass 5. The NAV block in the lower right hand corner of the HUD. I now see that the 90-degree error on (4) is well known and slated for repair in the next patch. So let's leave that out. What I'm seeing is that the NAV block info (5) disagrees with what is on the HSI time-to-next-waypoint readout. I'm going to fly the same mission and report back with more specific info.

Hello, I'm new to LOMAC, so this may already have been identified. The F-15 heading tape and HSI do not agree with one another. The HUD appears to carry the correct course information, the HSI is incorrect.