Jetfire

You're not the only one. GG mentioned that in 1.1 the server can pass it's scripts onto clients, which is great news.

Hajduk, I didn't realize you did not need another piece of software at the other end of the cable. So, the program I made might be able to be slightly modified to work with your setup. If you did need another piece of software, it would have meant a quite a bit more programming in C++. If you email me (su27jetfireAThotmail.com) or post in here the data format you need and the data you want to export from Lua, I can take a look at the program I made. I don't think I would have to change that much in my program to make it compatible.

Just saw this!!! omg very nice! Thanks SK and Alfa!

When you press ctrl+keypad0, your view should lock in the cockpit (cockpit view toggle). If you changed this cockpit view toggle key, just press the new key you assigned it to. Also, this only works in 1.02. I haven't had any luck getting export.lua working in 1.1. Also, SK, if you know (or if anyone here might also know): is there any other ways to capture keyboard inputs with Lua scripts? You would think there would be. It would be kind of a hassle to make a program that uses directinput to capture keystrokes then pass it to LockOn.

http://www.waves.utoronto.ca/~pavacic/lomac/keyboard/lights.zip (Thanks to SwingKid) http://www.lomacfiles.com/modules.php?name=Downloads&d_op=viewdownloaddetails&cid=13&lid=246&title=Aircraft%20Strobe%20Lights#dldetails (Thanks to Merlin and Lomacfiles.com) Issues: -all 3 lights flash at once -multiple keys must be pressed to turn lights off or on Plz post back here if there's any problems.

LockOn 1.0 demo was the same way. 640x480 could be used, even though it looked horrible, and you had to fix the config files. When 1.0 was released, the game would crash if you tried 640x480 in the config file. So, I'm wondering if 1.1 will crash if I try to put 800x600 in the config file once 1.1 comes out. I hope not.

The way LockOn 1.02 runs right now, I get avg 35 fps with textures on high, terrain medium, water low, effects low, and resolution 800x600. With AA turned on for my vid card, the game looks even better. Now, in the 1.1 demo, there is no 800x600 option. Why? It was there in 1.02, and now it's removed? How difficult would it have been to just leave it as an option since it was already implemented in 1.02? I would rather play with my settings I have now, then to have to increase to 1024x768 and have everything in the game look bad because I had to lower all the other options for performance. So, I ask, can you please put 800x600 back? :(

I really appreciate Eagle Dynamic's work and they are doing an excellent job. Last few days, there has been alot of negative feedback regarding Starforce, for example, people saying they won't buy FC. Bottom line is, this is just a game, ED works hard to give us LockOn, and without LockOn, what would we have? Face it, there's some aspects in LockOn that are very hard to find in other flight sims. So, yes, I will buy it. I am a satisfied and loyal customer because I'm very happy with every version of LockOn. They have not let me down. Bugs you might ask? Everything has bugs, welcome to reality. The funny thing is, this poll has 9 members at the moment who say they won't buy FC. Sooo, they have to be reading the forums to see this poll, but hey wait, they said they don't have any interest in buying FC. Can someone explain why they're here reading a LockOn FC forum if they are no longer interested in LockOn: FC? Sigh. As a little girl on some show once said, "Whiners are weiners" lol For those who are complaining about StarForce saying they won't buy 1.1: "You get more bees with honey then you do with vinegar". I heard this one a few decades ago. Try a more constructive approach next time instead of saying "I won't buy it". Anyways, keep up the excellent work ED, you're doing a great job and I know you won't let us down.

Very nice Strikemax!!

Yeah I hope you're right. They better not be teasing us lol

If you want to see an su-17 when you're in an su-25, you need to copy su-17.cmd over su-25.cmd in your Lock On\bazar\world\shapes folder. Make sure you backup su-25.cmd. Of course, doing this, you will see your loadouts in strange positions on your su-17, so you would also have to edit the pylon positions in your MEinit.xml in your Lock On\ME folder. Make sure you backup your MEinit.xml if you edit it.

Can anyone confirm if the FM of the Su-27 in the demo is or is somewhat close to the FM in the beta (or the final release)? I don't want to get my "hopes up" but from the demo the Su-27 flies awesome (turn rate, high aoa control)! Finally an Su-27 that has teeth ;)

It's probably something on the website that finds out your language (either by country or by language) then loads the page appropriately.

hmm... didn't seem that hard to land. I even landed it once ( out of 5 times ) on grass off the runway. Good fun ;)

no 800x600 resolution????? That sucks, now I can't run it!

Thank you for reply, just sent you a message.

hello Chizh and Shepski, I sent you both a very important private message. Please confirm whether you read it or not. This is a very serious problem and results could be disastrous if this is not addressed.

hi again Galevsky ;) I'm pretty sure I read that objects on the map will be available in the Lua scripts, it would be nice if a dev could confirm this however.

3rd place! Make sure you don't vote NFS: Underground 2 for any of the other games ;)

Ahh! That is true Dmut! So, any addon file has to have it's own distinct filename, so there would have to be some type of association made within the addon Lua file that associates it with the original file it will modify. This association would have to be made because, to my experience, most Lua script functions in LockOn don't share the same scope. So, perhaps to an addon that modifies "cockpit.lua", we could have a function call dofileafter( "cockpit.lua" ) at the very beginning of a new file called "cockpit by Jetfire.lua". This function would make the association between "cockpit.lua" and "cockpit by Jetfire.lua". Just an idea...

Thanks Darkstar!

hi, I have made a few scripts that I find very useful, and I would like to share with everyone. The problem is, if I want to share a script that only modifies one function or one line, I have to get the person who downloads my file to overwrite the entire file, thus overwriting other modifications the person might have made. So, is there any way to go about this differently? Will Lockon compile/link any lua file within certain folders, or just the lua files that are already there? If the only way to do it now is to overwrite the files, here's a possible fix: make it so Lomac will compile all Lua scripts in a certain folder AFTER all other scripts have been compiled. So, for example, this folder was called Lua Addons. Say I wanted to modify cockpit.lua, I could put a file named "cockpit.lua" in the "Lockon\Lua Addons" folder, containing only the functions or variables that were changed. Then, LockOn would compile the "cockpit.lua" in the Config/Views folder, then it would compile the "cockpit.lua" in the Lua Addons folder, so the new variables and functions would be redefined by the new file.

This mod will give everyone without TrackIr a bit more situational awareness without having to wear out your hat switch. The original Natural Head Movement (CTRL F1) only moved a small amount above the cockpit - now, this mod will make the view go to at most 100 degrees above the hud (looking straight up at the canopy). Movements are smooth and head movement is based on how hard your plane is turning. Post here or contact me at su27jetfireAThotmailDOTcom if you have any problems. This mod will not let you look anywheres you can't already look with your hat switch. Sorry, just noticed you need to visit my site to download the Loman ZIP file, so go here: http://jetfire.freeserverhost.com/ [edit]Fixed url

It would be nice if we could have separate server options for plane padlock and missile padlock - plane padlock is very nice (maybe plane padlock range should be halved, when planes are clearly visible). Missile padlock, on the other hand, gives away a missiles position way too easily. Besides, when you're trying to avoid missiles, you usually beam them or put them on your six, so you don't have to move your views constantly, you just have to look in a certain direction for awhile for vapor or smoke from the missile. Missiles aren't supposed to be so easily seen and padlock makes it just too easy. It would also be nice if the padlock buttons were set like in 1.01 - 1 push to padlock, another push to un-padlock. Another button could be used for padlock cycle. So, - plane padlock and missile padlock on / off in the options - plane padlock range set to 5 or 7 kms? - padlock button is a toggle, 1 press padlocks nearest plane to the center of your view, another press stops padlocking and leaves view where it is. A second button could be used for padlock cycle

MrWolf, I'm seriously overhauling the code to do alot more stuff, so I'll get back to you when it's up and running.