Widescreen Gaming Forum

[-noun] Web community dedicated to ensuring PC games run properly on your tablet, netbook, personal computer, HDTV and multi-monitor gaming rig.
It is currently 09 Jun 2026, 11:04

All times are UTC [ DST ]




Post new topic Reply to topic  [ 33 posts ]  Go to page 1, 2, 3, 4  Next
Author Message
PostPosted: 02 Jun 2006, 15:03 
Offline

Joined: 26 Apr 2006, 16:29
Posts: 71
Hi jkeefe,

Thanks for the feedback, it's strange it didn't work for you as I gave the same fix to another customer on our forums and it worked fine for him ????

I will have to dig a bit more then :-)


Top
 Profile  
Reply with quote  
PostPosted: 02 Jun 2006, 15:26 
Offline

Joined: 21 Apr 2006, 17:17
Posts: 643
Richie,

It's gotta be something in another .cfg or .lua file then. Or that other guy is running Lock On 1.02 while I have Flaming Cliffs (1.1) and there is some difference. Do you have this title in-house and is the full range of view zoom working for you? If so, is it 1.02 or 1.1 Flaming Cliffs?

If I need to install 1.02 for testing purposes I can do that easily without messing up my real install.

I'm very happy to see Matrox is working on this; Lock On is simply amazing in triplehead even when it's unplayable because of these view zoom issues. If I could get it working like it's suppossed to, I would be ecstatic.


Top
 Profile  
Reply with quote  
PostPosted: 28 Jun 2006, 03:22 
Offline

Joined: 28 Jun 2006, 03:11
Posts: 1
The problem is aspect ratio, which is stuck at 4:3 (1.33). Try changing it to whatever ratio you have (f.i. 1680/1050=1.6). Worked for me.

Lock OnConfiggraphics.cfg:
Code:

       Simulation
       {
           resolution = {1680, 1050};
           bpp = 32;
           fullscreen = 1;
   //        aspect = 1.333333373;
      aspect = 1.6;
       }


But every time you change something in options, the game resets it back to 1.33, so you have to edit it again.


Top
 Profile  
Reply with quote  
PostPosted: 28 Jun 2006, 16:31 
Offline

Joined: 21 Apr 2006, 17:17
Posts: 643
I have set the proper aspect ration for 3072x768, which is 4.000. This is not the cause of the problem.

I have not been able to experiment with this because my main video card failed, but I will spend some time on it when a relacement arrives.


Top
 Profile  
Reply with quote  
PostPosted: 04 Jul 2006, 06:07 
Offline

Joined: 21 Apr 2006, 17:17
Posts: 643
Ok, I got a new videocard (7900GT) and reverted to Lock On 1.02 to test with a pre-Flaming Cliffs version of the game. I am still stuck with a way-too-close max zoom out.

Richie, at this point I am pretty frustrated; I've done everything everyone's suggested but nothing seems to be working. I even tried running at 2400x600 in case the problem was specific to the resolution. Has anyone actually got this thing working with appropriate cockpit zoom and a triplehead resolution? I have yet to see a screenshot...

Please tell me what you would like me to do. Step-by-step instructions, post on the Matrox boards, post on the Eagle Dynamics boards, whatever.


Top
 Profile  
Reply with quote  
PostPosted: 04 Jul 2006, 15:56 
Offline

Joined: 26 Apr 2006, 16:29
Posts: 71
Hi Jkeefe,

I was looking at my View.lua file and it doesn't have any of those settings you listed????

I did find another setting in the file cockpit.cfg in the Lock OnConfigs folder. In that file there is a setting called FOV. I changed it to 5 and it seems to work but as soon as I move the view to look either let or right it returns to the previous state of being too zoomed in.

I also found a file called Cockpit.lua with the follwoing settings

-- Copyright (C) 2004, Eagle Dynamics.
-- Cockpit view scripts (F1, Ctrl-F1, Alt-F1)
-- Uses SnapViews.lua and Serialize.lua

CockpitMouse = false
CockpitMouseSpeedSlow = 1.0
CockpitMouseSpeedNormal = 10.0
CockpitMouseSpeedFast = 20.0
CockpitKeyboardAccelerationSlow = 5.0
CockpitKeyboardAccelerationNormal = 30.0
CockpitKeyboardAccelerationFast = 80.0
CockpitViewAngleMin = 20.0
CockpitViewAngleMax = 170.0
-- If CockpitViewAngleDefault is not set here then option value is used
-- Remove comment "--" in the next line and set your custom value:
--CockpitViewAngleDefault = 60.0
CockpitKeyboardZoomAcceleration = 300.0
DisableSnapViewsSaving = true
UseDefaultSnapViews = false
CockpitPanStepHor = 45.0
CockpitPanStepVert = 30.0
CockpitNyMove = true
CockpitHAngleOrigin = 0.0
CockpitVAngleOrigin = -9.5
CockpitHAngleAccelerateTimeMax = 0.15
CockpitVAngleAccelerateTimeMax = 0.15
CockpitZoomAccelerateTimeMax = 0.2
HAngleMaxDefault = 170.0
VAngleMinDefault = -65.0
VAngleMaxDefault = 170.0
HAngleMaxSu25 = 170.0
VAngleMinSu25 = -65.0
VAngleMaxSu25 = 170.0
HAngleMaxF15 = 170.0
VAngleMinF15 = -65.0
VAngleMaxF15 = 170.0

CockpitLocalPoint = {}
CockpitLocalPoint[PlaneIndex.iSu_27] = {8.05, 1.35, 0.0}
CockpitLocalPoint[PlaneIndex.iSu_33] = {8.35, 1.35, 0.0}
CockpitLocalPoint[PlaneIndex.iSu_25] = {3.0, 0.276, 0.0}
CockpitLocalPoint[PlaneIndex.iSu_39] = {3.0, 0.276, 0.0}
CockpitLocalPoint[PlaneIndex.iMiG_29] = {4.76, 1.284, 0.0}
CockpitLocalPoint[PlaneIndex.iMiG_29K] = {4.9, 1.254, 0.0}
CockpitLocalPoint[PlaneIndex.iA_10] = {3.991, 1.507, 0.0}
CockpitLocalPoint[PlaneIndex.iF_15] = {6.4, 1.218, 0.0}

function GetCockpitLocalPoint(iType)
local p = CockpitLocalPoint[iType]
return p[1], p[2], p[3]
end

The ones in Bold are the ones I changed. I can pull out a bit further but looking at your single head screen shot I still cannot see the legs. :-(


Top
 Profile  
Reply with quote  
PostPosted: 04 Jul 2006, 17:45 
Offline

Joined: 21 Apr 2006, 17:17
Posts: 643
I was looking at my View.lua file and it doesn't have any of those settings you listed????
Those are settings added in the Flaming Cliffs addon for more view customizability.

I did find another setting in the file cockpit.cfg in the Lock OnConfigs folder. In that file there is a setting called FOV. I changed it to 5 and it seems to work but as soon as I move the view to look either let or right it returns to the previous state of being too zoomed in.
If I change this to 5 it seems to have no effect. I can slew the view left or right using the numpad keys and the FOV does not change.

I also found a file called Cockpit.lua with the following settings
Now I'm confused, as the contents of that file are from Flaming Cliffs 1.1 or later, not Lock On 1.02. Which version are you using? If you are using Flaming Cliffs, why don't you have the same view.lua file as I did before I reverted to 1.02?


Top
 Profile  
Reply with quote  
PostPosted: 04 Jul 2006, 19:44 
Offline

Joined: 26 Apr 2006, 16:29
Posts: 71
Hi JKeefe,

Here is what I did, I installed Lock-On form the CD. Went to Avault.com and got the 1.00-1.02 patch and that is it. These are the files and settings I am left with ????


Top
 Profile  
Reply with quote  
PostPosted: 05 Jul 2006, 06:13 
Offline

Joined: 21 Apr 2006, 17:17
Posts: 643
Ok, that means you have Lock On 1.02 (without Flaming Cliffs).

Sorry, I was looking at cock;it.cfg, not cockpit.lua. I have my cockpit.lua set as you do, CockpitViewAngleMax = 170.0.


Top
 Profile  
Reply with quote  
PostPosted: 05 Jul 2006, 15:26 
Offline

Joined: 26 Apr 2006, 16:29
Posts: 71
Hi Jkeefe,

With all those files set you should be able to pull out a bit more than the but still cannot see the legs. Unfortunately I cannot post any screens from here at work to show you what I mean :-(


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 33 posts ]  Go to page 1, 2, 3, 4  Next

All times are UTC [ DST ]


Who is online

Users browsing this forum: No registered users and 10 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron




Powered by phpBB® Forum Software © phpBB Group