Oolite test release 1.73

Hemlock · Post by **Hemlock** » Mon Aug 31, 2009 11:10 pm

Thanks Kaks.

zevans · Post by **zevans** » Tue Sep 01, 2009 1:09 am

El Viejo wrote:
It seems that D does not eject cargo. Shift R cycles the cargo, but I cannot eject it. Anyone else found this?

I occasionally get that. Since I can't figure out how to reproduce it yet I didn't mention it so far...

Website · Post by **Cody** » Tue Sep 01, 2009 6:29 am

In a way that's reassuring; at least it's not just me. I know it happens, but I can't make it happen.

Commander McLane · Post by **Commander McLane** » Tue Sep 01, 2009 8:06 am

Hemlock wrote:
I am getting a message that:

Anarchies 2.2.oxp
Interstellar_help.oxp
total_patrol.oxp

are incompatible with Oolite 1.73.....

Is this an error...or are there updated versions of these OXPs out there that I have missed?

Thanks

H

Hi! These are all mine.

I was away for the weekend and haven't even installed Oolite 1.73 yet. So please give me some days for making my OXPs 1.73-ready. With the fix mentioned by Kaks they'll probably work anyway, but I want to check if there are any issues with new/deprecated methods, and then upload new versions. May take a week or so, so please be patient.

Selezen · Post by **Selezen** » Tue Sep 01, 2009 9:04 am

Can I ask a daft question again?

I've been trying to get the shaders working on my laptop and was wondering what the minimum requirement is for shaders to work on a gfx card. I have a GeForce FX 5200 Go and according to the specifications it has support for vector and pixel shader v2. Is that enough?

If so would anyone know how to enable it? It this point I have Griff's models showing but no glowmaps.

Diziet Sma · Post by **Diziet Sma** » Tue Sep 01, 2009 9:27 am

I use the same card.. if you have the latest drivers from NVIDIA and set shaders to full in the F2 options, you should be good to go..

Hemlock · Post by **Hemlock** » Tue Sep 01, 2009 2:09 pm

Commander McLane wrote:
Hemlock wrote:
I am getting a message that:

Anarchies 2.2.oxp
Interstellar_help.oxp
total_patrol.oxp

are incompatible with Oolite 1.73.....

Is this an error...or are there updated versions of these OXPs out there that I have missed?

Thanks

H
Hi! These are all mine.

I was away for the weekend and haven't even installed Oolite 1.73 yet. So please give me some days for making my OXPs 1.73-ready. With the fix mentioned by Kaks they'll probably work anyway, but I want to check if there are any issues with new/deprecated methods, and then upload new versions. May take a week or so, so please be patient.

No problem waiting. Unpack your bags before you unpack the files.

Meantime, I'll have a Trumble Burger with mushrooms and onions and sit back in my commodious Mosquito.

H

Post by **Eric Walch** » Tue Sep 01, 2009 2:19 pm

Commander McLane wrote:
Hemlock wrote:
.... total_patrol.oxp....

are incompatible with Oolite 1.73.....
... but I want to check if there are any issues with new/deprecated methods, and then upload new versions. May take a week or so, so please be patient.

At least total_patrol.oxp can be improved with 1.73, as it now it has a early message at the sun returning point. Look inside Oolite for the new route2patrolAI. With Oolite 1.72 all oolites own route2vipers just burned in the sun because they tried to turn at the fuel skimming point what was way to late.

Griff · Post by **Griff** » Tue Sep 01, 2009 2:31 pm

@Selezen, if the ships look bumpy but with no glows etc, then Oolite could be using simple shader mode, try changing it to 'full', then exit the game and restart it to apply the change

Selezen · Post by **Selezen** » Wed Sep 02, 2009 8:00 am

Right, that's a couple of ideas there, thanks! I'll give them a try tonight.

Commander McLane · Post by **Commander McLane** » Wed Sep 02, 2009 10:45 am

Eric Walch wrote:
Commander McLane wrote:
Hemlock wrote:
.... total_patrol.oxp....

are incompatible with Oolite 1.73.....
... but I want to check if there are any issues with new/deprecated methods, and then upload new versions. May take a week or so, so please be patient.
At least total_patrol.oxp can be improved with 1.73, as it now it has a early message at the sun returning point. Look inside Oolite for the new route2patrolAI. With Oolite 1.72 all oolites own route2vipers just burned in the sun because they tried to turn at the fuel skimming point what was way to late.

In total_patrol I dealt with that by (1) massively increasing the desired range from 25000 to 125000 and (2) giving all police ships a heat shield.

But yes, I already updated total_patrol according to the current patrolAIs. Will be released as soon as I tested it.

By the way: There are some small and inexplicable differences between route1patrolAI and route2patrolAI, e.g. in the HEAD_FOR_foo states:

route1patrolAI:

Code: Select all

        "INCOMING_MISSILE" = (
            fightOrFleeMissile, 
            setTargetToPrimaryAggressor, 
            deployEscorts, 
            "setStateTo: INBOUND_LOOT", 
            groupAttackTarget
        );

route2patrolAI:

Code: Select all

        "INCOMING_MISSILE" = (
            fightOrFleeMissile, 
            setTargetToPrimaryAggressor, 
            deployEscorts, 
            groupAttackTarget, 
            "setStateTo: OUTBOUND_LOOT"
        );

Don't know, though, whether the order of groupAttackTarget and setStateTo: matters. Oh, and by the way, the INBOUND_LOOT in the first example is a c&p-bug in the HEAD_FOR_WITCHPOINT-state, should be OUTBOUND_LOOT.

Another difference is that route1patrolAI switches to gotoWaypointAI, while route2patrolAI has its own WAYPOINT-states.

Post by **Eric Walch** » Wed Sep 02, 2009 11:31 am

Commander McLane wrote:
Don't know, though, whether the order of groupAttackTarget and setStateTo: matters. Oh, and by the way, the INBOUND_LOOT in the first example is a c&p-bug in the HEAD_FOR_WITCHPOINT-state, should be OUTBOUND_LOOT.

Another difference is that route1patrolAI switches to gotoWaypointAI, while route2patrolAI has its own WAYPOINT-states.

That INBOUND_LOOT is definitely a copy&paste bug introduced already in 1.72 while fixing an other bug with that line.

The different waypoint handling has historic reasons. In the past the waypoint was always dealt within the AI itself. Already with 1.65 AI was completely reworked for the main route but no time was spend on the AI for route 2 (planet-sun). And as both work, why spend time in changing it. Changing itself takes no time but to do it well it must also be tested than to be sure you miss no exceptions.

Specially here are two different external AI's called than from within one state, that both need a different RESTARTED reaction. In the route1patrol a special trick is introduced to let it work. There the order of ("setStateTo: INBOUND_LOOT", groupAttackTarget) is very important as it changes the returnadress (returnstate) for the final "setAITo: interceptAI.plist" were all this ends as reaction on a missile attack.

The current OUTBOUND_LOOT can even be removed from your example as it only is called when the AI is already in interceptAI.plist and that has no such state. "groupAttackTarget" is a command with immediate reaction that makes that the line "GROUP_ATTACK_TARGET" = (setTargetToFoundTarget, "setAITo: interceptAI.plist"); is executed before it evaluates the following command in that line.
No real harm as it than just will do nothing but I'll change that line it in trunk.

Selezen · Post by **Selezen** » Thu Sep 03, 2009 9:28 pm

Good news, everyone!

I have updated my drivers from V4.0.1 to V6.15.13 and I HAZ GOT SHADERZ!

Oolite's menu options said that Shaders were unavailable before, and after the driver update everything was enabled. I'm a happy man!

Thanks for the advice!

Cmd. Cheyd · Post by **Cmd. Cheyd** » Thu Sep 03, 2009 9:39 pm

WOOT Selezen!

Simple or Full?

Either way, it's got to be a huge jump forward in the visuals!
Congrats!

Selezen · Post by **Selezen** » Thu Sep 03, 2009 9:49 pm

I have the option of Simple or Full! Shaderz to the max.

Jeez, I gotta stop typing like an emo teen...