Hi All,

As I said above, I'm new to LOMAC and have just started on the huge learning curve, so please forgive me if these seem to be silly questions.

I'm having two issues. The first is with the views. When I look around the cockpit or out the canopy, the view jumps back to the front view almost instantly (This also happens when outside looking at the plane in flight). Is there a setting I can change so that if I look at the particular instrument or out the side of the canopy, it will stay there until I press the key to go back to the default view. I know I can do this while holding down the shift key, but then some of the key functions are changed, so for example I can't keep my eye on a ground target or landmark while changing other things. I assume this has something to do with snap views but I can't figure it out.

The second issue is that when I select weapons, they all start firing automatically, even before I press the space or return key.

You help will be greatly appreciated.

Start your journey by using my site- click sig. There you will find all the basic setup, hardware discussion, patches, and links to the best training available- www.flankertraining.com

As for these 2 specific questions:

In the absence of a TRACK IR- I reckon you are using the keyboard to look around? It sounds to me like you are using the snap views. I think it is the number pad that is the default head movement. If you use the 4 & 6 keys you will move yer melon left/ right and it should stay where you left it. A snap view is exactly that- it shows you something, and snaps back.

Your weapons are shooting on their own? LOL... That's messed up. I think I need more specific information- such as tell me EXACTLY WHAT YOU ARE DOING key by key.

Hi konkussion,

Thanks for the reply. Quite incidentally to this problem I'm having, I'd actually been to your site and read a great deal of helpful stuff there about getting started (thanks for your efforts there) and also downloaded Ironhand's GUI & Mission Builder 2 part video which I watched last night. After watching I loaded up the mission and this brought up a few other issues. For example, in the tut he uses HOME-SHIFT and HOME-ALT to start the engines which didn't work on mine. I found that I had to use SHIFT-PGUP and ALT-PGUP. I also found that I need to use # to bring up the communications menu instead of / which he mentions.

This started me thinking that maybe these issues are related, and related to the fact that I have a UK keyboard, although I'm not sure why that should make a difference because it's mapped as a UK keyboard in Windows and even if the keys are in different places physically, they should still be mapped to the same commands ?!? I'm also pretty sure that someone else would have had this issue if it was that. By the way, in case it's of importance, I have LOMAC v1.01 patched to v1.02.

In answer to your question though, yes at the moment I'm using the keyboard for everything. I've only had LOMAC for a few days now and the old joystick I have from my sim days years ago is not suitable so I will be investing in a new USB one shortly, assuming of course I can figure out these issues which are making it impossible to do little more that sightsee and do some aerobatics.

With regard the "auto firing" issue. I've tried it in both the instant mission and in Ironhand's A-10 mission and in all cases as soon as I press the 7 key, missiles start flying with no other input from me. For example, in the instant mission from the main screen I click on "FLY". The mission opens in flight with several targets ahead. I press "s" to start. Even if I press nothing else and press "7" right away all the missiles are released and the canon starts firing short bursts (I know this because I see puffs of smoke from the front and if I'm low enough, I see the rounds hit the ground). If I press the space bar the canon will begin firing continuously and when I release, it will go back to bursts until it runs out of ammo. Oddly enough (or maybe not) if I press the "1" key which appears to change the NAV mode, the firing stops.

Any ideas on this oddity? Clearly from Ironhand's video, the views and firing should work the way I expected right out of the box, but on mine they don't for some reason

There may be some issue with the UK keyboard.

Ironhands' tutorials are likely to be referring to versions post-Flaming Cliffs. This is version 1.1 or later with the patches that came out since then. There were several key changes made in this version- the series of keys for engines start/shutdown were one of the series changed. Your 1.02 version should use "page up/down".

Now- the auto-blasting. I must say- this is a first. Since I'm mostly at a loss- try the following while I think about this..

Turn off "easy radar" in the options. You can either do it in the UI, or on the fly with the keys "shift+I" See if that changes anything.

Hi,

I had already turned off easy radar. I've also turned off easy flight and combed through the options looking for anything else which might cause things to happen automatically. At the moment I'm busy combing through the config files to see if there is anything that jumps out that could possibly cause a problem but so far I've not seen anything. I even tried a reinstall yesterday to see if it was the v1.02 patch which messed things up, but it does the same thing with a clean install, with and without the patch, so I patched it again.

Next I might try clearing all the view and snap keys and then reassign them and see what that does.

Your thoughts ?

I can think of NO built-in feature or anything else that would cause weapons to auto-fire. You have a keyboard issue of some kind.

There are commands being sent inadvertently.

Starting with version 1.02- there were 2 firing commands for the US aircraft.


Space bar- guns only
enter key- launch weapon/ drop bomb.

Verify that these commands are properly assigned in the buttons menu of lockon.

WooHoo, I fixed it !!

I discovered an ini file in the /input folder which I recognised as my UPS. During install the game must have thought this was an input device as it's connected via USB. So I checked in the options, and sure enough it was listed in the drop down menu and had, you guessed it, assigned various functions including both fire keys and the centre view to various "buttons". Not that it has any buttons so I assume it was an interpretation of the status input from the UPS to the monitoring software. So I cleared all the button assignments and all is well with life once more.

Now I can get down to the business of enjoying my learning cure instead of tearing my hair out

As konkussion intimated, the engine controls on IronHands Getting Started video are different becuase he was using Flaming Cliffs and you only have the basic Lockon patched to v1.02, your radio command is different because (like me) you have a UK keyboard, hence it is the # key.