trouble with AOB and OLC uber [Archive] - SUBSIM Radio Room Forums

View Full Version : trouble with AOB and OLC uber

tmdgm

02-28-09, 11:11 PM

I've been using OLC uber and am having trouble with AOB with certain ships. Can't remember all the ships I've been having trouble with, but last mission was with a granville type freighter and a meduim cargo. The medium cargo AOB seemed ok, or close enough.

But on the granville freighter, it always seems like I get the range which seems ok, then rotate to the length (which was 78.3), and the AOB on many occasions reads more than 90 deg (anything above 15deg on the length is >90), which in all the cases, is no where near accurate.

Is there somethign I'm missing? Is it something with addon ships?

tmdgm

02-28-09, 11:35 PM

also forgot to mention that the readme has a link saying uber is slightly different than gui. but the link doesn't work. Any way to get this?

UberTorpedo

03-01-09, 11:36 AM

tmdgm

Click on my filefront link below. There's a lot of info on OLC's mods there. :hmmm:

cheers

tmdgm

03-01-09, 11:56 AM

tmdgm

Click on my filefront link below. There's a lot of info on OLC's mods there. :hmmm:

cheers

Ok, thanks. I think i have that extra video, it just tells you that it's not mastx2 anymore.

Somethign with AOB seems off, but only on certain ships. For example, I was using attacking a Granville Freighter. The mast is 20.9 with length 78.3. Anything above 15 on the vertical scale reading and you get >90 AOB. In the case I was in last night, that was impossible.

The medium cargo ship I attacked was right behind it and gave an accurate AOB.\

Just not sure if I'm missing something obvious

UberTorpedo

03-01-09, 09:52 PM

tmdgm

I vaguely remember some discussion about the mast heights not being
correct for some of the "community units" ships. :doh:

Does anyone else out there remember anything along that line?

Was it bigboywooly that had a fix??? Can't remember...

Are you using "community units"?

Pisces

03-02-09, 07:03 AM

tmdgm

03-03-09, 09:04 PM

I don't know about specific ships. But yes, if the mod creator (3rd party ship modeller) didn't modify the recognition manual files you're in trouble. Then you would need to ask your watch officer for a range when surfaced, and use the range-finder backwards to asses mastheight.

At some OLC GUI version it was discovered the NKBL ship had a wrong mastyheight (needed a fix to 19.3m), but that was before GWX 3 was released. So I guess it's not an issue anymore.

Thx. That's what I was thinking, that some ships didn't work for OLC. I'm using GWX2.1 and OLCuber. They're the only mods i'm using. I had a feeling when one of the ships (glanville freighter) had an AOB >90, and a medium cargo (probably stock ship) seemed to have the correct AOB.

I guess I'll just have to live with it. I've had it happen with a few ships so far. I wonder if it's something with the mast height X2? Because in the original OLC, you had mast height X2. Now it's just mast height.

If anyone knows a fix, please pass on.

Pisces

03-04-09, 07:09 AM

I use the original OLC Gui, so if you can figure out which files are for that Granville-type freighter (I don't have a clue how Sh3 decodes the name to the folder structure)than I can check what I have.

makman94

03-04-09, 12:13 PM

hello tmdgm,

i am not sure that i had understand you correctly but do this : load olc gui 1.2.7 and tell us if you have the problem.if it appears ...please name the exact name of the ship.

bye

tmdgm

03-04-09, 11:33 PM

hello tmdgm,

i am not sure that i had understand you correctly but do this : load olc gui 1.2.7 and tell us if you have the problem.if it appears ...please name the exact name of the ship.

bye

So maybe it's an OLC UBER issue? Is OLC GUI more up to date? Can I load OLC gui and OLC uber at the same time? Don't want to disable uber cuz of the visuals. The exact name of the ship in Uber is Granville type freighter. I've had it happen to other ships as well. It does seem to be ships that aren't stock, like a medium cargo for example is right on with AOB.

makman94

03-05-09, 01:31 AM

So maybe it's an OLC UBER issue?-didn't say that Is OLC GUI more up to date? Can I load OLC gui and OLC uber at the same time?-disable olc uber and run only the olc gui 1.2.7 Don't want to disable uber cuz of the visuals.- ?? you will run the olc gui 1.2.7 only for to test if you have the same problem with that ship The exact name of the ship in Uber is Granville type freighter-that is the name that you read in the rec manual? . I've had it happen to other ships as well. It does seem to be ships that aren't stock, like a medium cargo for example is right on with AOB.
do the above and write the exact name of the ship that the problem will appear,if appear (with olc gui 1.2.7 enabled)(also write its specifications, mast, length)

bye

makman94

04-11-09, 04:16 AM

@tmdgm, i found yesterday the ship that you are talking about and you are right . both mast and length are not correct (you said that you play gwx 2.1 ). find inside data/sea the NGRA_ folder.inside you will find the cfg of the ship.

set at the length of the ship 91.5 and at mast 21.3 and you are ready to go !

(warning: for the range measurments you will measure the mast with the flag AND THE FLAG )

try it and report back

bye

onelifecrisis

04-11-09, 04:39 AM

If anyone knows a fix, please pass on.

There is a fix. Upgrade to GWX3. :salute:

(and don't use community ships ;) at least not without checking their measurements)

makman94

04-11-09, 05:04 AM

There is a fix. Upgrade to GWX3. :salute:

(and don't use community ships ;) at least not without checking their measurements)

hello OLC,(how are you ? -good to see you around !)

your suggestion will do nothing becuase gwx3 uses the same values for length and mast with gwx2.1 for the NGRA_. ( 78.3 to 91.5 is big difference)

bye

onelifecrisis

04-11-09, 06:57 AM

hello OLC,(how are you ? -good to see you around !)

your suggestion will do nothing becuase gwx3 uses the same values for length and mast with gwx2.1 for the NGRA_. ( 78.3 to 91.5 is big difference)

bye

Oh, I was under the impression that those things were fixed in 3. :roll:
My bad.