View Full Version : LOMAC Tweaks and Tips
Right, looks like this forum is expanding a bit so here's a thread for tweaks, tips and tricks.
I'll start the ball rolling with my "Mouse Look in Cockpit - F1 View" tweak:
Navigate to your Lock On install folder and then in to the Config/View subfolder and look for a file called view.lua
Open this file with notepad or any other text editor and about a dozen lines from the top you will see an entry marked:
CockpitMouse = false
Make this into:
CockpitMouse = true
Save the file, overwriting the original and fire up LOMAC. Bingo, the mouse now allows you to look around the cockpit. Hand when used with the zoom in and out keys to look closer at the guages and in particular the radar and RWS on Ruskie planes.
Have pHun!
I use EditPadPro and you won't find a better notepad replacement:
http://www.madcowmoo.com/lomac/tutorials/editpadpro/EditPadProv612.rar
Tower: "Hawk 20, is this the same aircraft declaring emergency about two hours ago ?"
Pilot: "Negative, Sir. It's only the same pilot."
Wes - do you know of a way for the default zoom view in cockpit to be altered?
Whenever I choose to 'reset' or centre my view, it's too close - I can't see anything below the artificial horizon, meaning I have to sit further back! A default zoom that's a little further back would be great. Can't see anything in the view.lua file that looks like what I need...
Wes - do you know of a way for the default zoom view in cockpit to be altered?
Whenever I choose to 'reset' or centre my view, it's too close - I can't see anything below the artificial horizon, meaning I have to sit further back! A default zoom that's a little further back would be great. Can't see anything in the view.lua file that looks like what I need...
You want this default with or without TrackIR? In FreeTrack I can set the default Z axis wherever I want so set it back a little further and have key-bound a button on the joystick and mouse to get me back there if I wander away from it.
If you are meaning just a bog standard change of default rest view, i.e. by hitting Keypad 5 followed by Keypad Enter then let me have a look.
Yup - bog standard. I know about the backspace, num5 etc.
Ta!
Cheers Exo, saves faffing with the numpad keys :D
Right epoch, here we go, download this:
http://www.madcowmoo.com/lomac/tutorials/lomacconfigutil/MadCowMoo_LOMACConfig.rar
Drop it in yer LOMAC core directory and then get in here and make the settings for say the F-15 look like this:
http://www.madcowmoo.com/lomac/tutorials/lomacconfigutil/config1.png
It's the settings I use for the F-15. Unfortunately, after the patches and FC add-on, they changed all the config files so a lot of old forum posts about FOV's etc are no longer applicable. Also, views for the aircraft were split out but then recombined in the lua files. It's a nightmare to follow but I'll keep you up to speed with what I know, when you need it.
WARNING: Do not feck around with the LUA files by hand or you will soon find your install useless. Unless of course you know what you are doing.
This tweak makes it possible to look all the way back over your shoulders without "bumping" into the headrest etc. Greatly improves SA. Recommended for TrackIr and FreeTrack users and practically does away with the need for the F4 view -
Be VERY careful with this one, backup your sever.lua file first.
Navigate to your Lock On install folder and then in to the Config/View subfolder and look for a file called server.lua
Open this file with notepad or any other text editor and at lines 46 to 53 are the settings for Camera angle limits which should look like this:
-- Camera angle limits {horizontal angle max, vertical angle min, vertical angle max}
CameraAngleLimits = {}
CameraAngleLimits[PlaneIndex.iSu_27] = {140.0, -75.0, 90.0}
CameraAngleLimits[PlaneIndex.iSu_33] = {140.0, -75.0, 90.0}
CameraAngleLimits[PlaneIndex.iSu_25] = {95.0, -65.0, 90.0}
CameraAngleLimits[PlaneIndex.iSu_39] = {110.0, -80.0, 90.0}
CameraAngleLimits[PlaneIndex.iMiG_29] = {140.0, -75.0, 90.0}
CameraAngleLimits[PlaneIndex.iMiG_29K] = {140.0, -65.0, 90.0}
CameraAngleLimits[PlaneIndex.iA_10] = {140.0, -65.0, 90.0}
CameraAngleLimits[PlaneIndex.iF_15] = {180.0, -65.5, 115.0}
Try some of these to see if you like them, I recommend the F-15 one first as you can now see all the way behind you over the cockpit seat:
horizontal angle max is horizontal angle of freedom.
vertical angle min is downward angle of freedom.
vertical angle max is upward angle of freedom.
Recommended Values:
A-10:
horizontal angle max = 180.0
vertical angle min = -72.5
vertical angle max = 115.0
Extended 50 degree horizontally and 7 degree downward.
There is a big headrest prevent you from seeing engines and tail fins.
But you can see 6 o'clock high clearly now.
And you can check chaff and flare counters on the right console much easier.
MiG-29,Su-27 and Su-33:
horizontal angle max = 145.0
vertical angle min = -65.5
vertical angle max = 115.0
Extended 15 degree horizontally.
You can see your 5 and 7 o'clock better.
Su-25:
horizontal angle max = 139.0
vertical angle min = -69.0
vertical angle max = 115.0
Extended 44 degree horizontally and 4 degree downward.
Not much improvement in situation awareness because of the ristrected view by window frames.
F-15:
horizontal angle max = 180.0
vertical angle min = -65.5
vertical angle max = 115.0
Extended 45 degree horizontally.
Great improvement in situation awareness.
You can see your 6 o'clock very clearly.
Take off and look back! You see the runway you just departed from.
Be VERY careful with this one, backup your sever.lua file first.
Anyone care to give us some cool settings for the Su-39?
Ground based early warning radar communicates with Russian jets, Su 33 & 27 & MiGs.
I'm not sure if the F15 has a simular data link.. need to test. (but i know nothing about the F-15 radar etc)
It provides simular info to that of awacs. You get info on your HDD of enemy aircraft.
Something to be remembered when making missions and flying them.
Just thought i'd share this little tip bit.
http://forums.eagle.ru//showthread.php?t=29288
MISSION EDITOR beta
LOME alpha public version
This is the first public version of LOME (LockOn Mission Editor). This is not the definitive version, and I am open to any suggestion.
Be careful, the import/export is not complete, some data are not currently available. You can normally import any mission file without any risk BUT export will generate a mission with missing information. Take care to not export it on a current mission you want to keep!!!
What is working
Basic import/export from LockOn game (if available on the system)
Create a new mission from scratch
Load/save in LOME format
Add/del/modify waypoint
Define task on waypoint (land/take off does not work when export due to LockOn bug)
Add ship/plane/vehicule/helicopter
Set plane payload/fuel
Set meteo
Set mission/coalition/group name
Duplicate group/subgroup/unit
What is not working/known bug
waypoint tasks: land, takeoff
Helicopter payload
fuel tank does not change total fuel quantity
load/use/save predefined payload
view filter
player options
You have a crash/a bug?
Please send me the lome.exe.log in the LOME directory if there is one. Send it to lome (at) dartsite (dot-no-spam) org with description. If a mission cause crash/problem, could you send me too?
LOME 0.2 alpha: http://server.3rd-wing.net/public/DA...e/lome-0.2.zip
a little mod i 'knocked off'
http://www.lockonfiles.com/modules/Downloads/imageuploads/thumb/Playboy%20kneeboard.jpg
Ok i'm sure many have noticed that terrain, trees & building tend to pop up, change level of detail (LOD) suddenly etc. giving weird/ugly effects. Terrain panels, of different LODs is one of the worst i get.
I've managed to get rid of most of this and have smooth terrain to max view distances.
Alt. 7,200m
http://img175.imageshack.us/img175/1259/view7200xv6.jpg
Alt.1500m
http://img175.imageshack.us/img175/2189/view2000df0.jpg
I have NOT tweaked these...straight screenshots. (@100%quality)
All this stuff can be altered in the graphics.cfg file located in ..Program Files\Ubisoft\Eagle Dynamics\Lock On\Config
You can also use LoCFG utility, but i've had more joy doing it manually.
Here are the settings i have ended up with.. very different from the original. I've included Low & Medium setting even though i'm not using them, they have only been altered slightly. (I know mine work so i'm showing you ALL the altered sections). It's the High settings that you need.
The land LOD stuff is also important. (affects LOD in different weather/day time)
Here are my manually altered parts of my graphics.cfg file
Camera
{
current = "High";
Low
{
near_clip = 4;
far_clip = 200000;
structures = {30, 2000};
trees = {60000, 3000};
dynamic = {300, 20000};
objects = {3000, 40000};
mirage = {3000, 10000};
surface = {20000, 200000};
lights = {50, 10000};
lod = 0.7;
}
Medium
{
near_clip = 0.2;
middle_clip = 4;
far_clip = 200000;
structures = {40, 5000};
trees = {100000, 8000};
dynamic = {300, 20000};
objects = {3000, 50000};
mirage = {3000, 15000};
surface = {20000, 200000};
lights = {100, 30000};
lod = 1;
}
High
{
near_clip = 0.2;
middle_clip = 4;
far_clip = 200000;
structures = {200, 10000};
trees = {200000, 20000};
dynamic = {300, 20000};
objects = {5000, 80000};
mirage = {5000, 20000};
surface = {20000, 200000};
lights = {200, 80000};
lod = 1.5;
LandLodDistances
{
LandDay
{
L01 = 30000;
L12 = 50000;
}
LandNight
{
L01 = 30000;
L12 = 50000;
This is WIP as it were... any other tips/settings let me know.
And you may take a fps hit, just make a backup of your file first, just in case all goes fubar.
Ok i have what i think are the perfect settings for my rig. No pop up trees, buildings or terrain patches etc..
Toned down from the last time i posted...
Custom2
{
near_clip = 0.2;
middle_clip = 4.;
far_clip = 100000;
structures = {200, 10000};
trees = {8000, 12000};
dynamic = {300, 20000};
objects = {5000, 80000};
mirage = {3000, 20000};
surface = {15000, 100000};
lights = {200, 80000};
lod = 3;
LandDay
{
L01 = 20000;
L12 = 40000;
}
LandNight
{
L01 = 20000;
L12 = 40000;
:D
commando-101
20-05-08, 09:18
I admire you guys for your patience tweaking this & that!
Me... I just put it on highest default I can get away with & fly!
I've had horrible transparent buildings.. this fixes it.
Edit the \Lock On\Config\graphics.cfg
Change lines fogparam2=1.1 and ObjectFogMultiplier=0.6 to 0 and 0.2. You can experiment with this. The bigger the value the more object will fade in and you get disgusting transparency. I use values 0.4 and 0.2
Put ANY weapon on ANY plane! nice and easy to use.
hmmmmm lots of your fav weapon! http://www.mental-block.net/lockon/LOPE101.zip
vBulletin® v3.8.3, Copyright ©2000-2010, Jelsoft Enterprises Ltd.