I just uploaded v0.4 of Planetary Compass to add a model to it, as there seems to be an issue with the visual effects code that is making our old friend the zero-poly bug (or something similar) recur if an effect without a model is used in some cases.
Rese249er wrote:
EDIT: CargoSpotter appears to make items unscoopable. I'm removing it, but also poking around code to see if I can repurpose it in conjunction with AI Combat Assistant.
This may be a symptom of the same issue, so I've just uploaded v0.4 of Cargo Spotter with the same fix.
Anyway I've informed Cim about it so he can have a look in the trunk code, as visual effects should work without models (that being one of their features).
The glow from CargoSpotter would be useful to integrate into Military Targeting and AI Combat Assistant OXPs.
Already on my short term "todo" list for upgrades to the military targetting system, in addition to upgrading 2 other as yet unreleased oxps that are still betas and possibly one other oxp that is still on paper.
Take an idea from one person and twist or modify it in a different way as a return suggestion so another person can see a part of it that can apply to the oxp they are working on.
Right, thanks to some sterling effort from Cim, the visual effect bug is well and truly squashed. So I've updated Planetary Compass to v0.5. It now also uses bolt-on name packs for the moon names, at least one of which must also be installed for the OXP to function (multiple packs can be installed, and will give a wider variety of moon names).
Download details for all are in the first post of this thread.
Also I now have 1.77 (only) versions of WildShips and Vortex. These won't be uploaded and made generally available until the full 1.77 release, but if anyone is interested in a preview copy please PM me.
Downloaded and installed BETA laser boosters recently. Haven't purchased the actual boosters, but have had a couple of instances where my lasers have crapped out on me in the middle of a firefight. That was a hairy moment; good thing I've also got RepairBots.
Got all turned around, lost my nav connection... Where am I now?
Considering my side-mounts are mining lasers, I'm glad I haven't had that happen yet! When it does, I'm injecting outta there. The frequency is enough to add a bit of challenge, but not enough to tick me off and remove it. Maybe once I experiment with the boosters, wherever they are, I may sell those back depending on how often I get a laser crapping out in the midst of a firestorm.
Right now I'm in G3 at the Esmaonbe-Lezaer zero-d pair. I just bought the booster, so we'll see.
Got all turned around, lost my nav connection... Where am I now?
And next one, in collaboration with Svengali, an update for Planetfall that works properly with 1.77. It also has a few new little effects, courtesy of aforementioned collaboration.
Again to note that this OXP will only work with an up-to-date version of trunk. Download link is in the first post of this thread.
Edit: Please ignore this message, the OXPs I complained about ARE compatible with 1.76.1, my mistake is that I was still on 1.76
In the OXP List, the OXPs for 1.77 have a "Y" in the "C" column, erroneously indicating they are compatible with 1.76.1.
Not a major problem, but I had to downgrade a couple of OXPs again after upgrading them.
Maybe removing the "Y" from (or adding a warning to) the OXP list may prevent others from running into this?
It might also be considered to change the "C" column into two columns, one containing the number of the lowest version needed and one indicating the highest version supported by the OXP? But I guess this is a lot of work (especially to keep it up to date - I can imagine that the amount of maintenance which would go into that would be unfeasable).
Anyway, a big thumbs up for the hard work that folks put in those new OXPs!
Last edited by Gimbal Locke on Thu Nov 01, 2012 12:14 am, edited 3 times in total.
Just to be clear - aside from Planetfall and (Neo)Docklights, none of the OXPs in this thread are compatible with 1.76.1 (although nor are any of them on the table). And for both PF and DL, there are 1.76.1 compatible versions of both which are the ones on the wiki and available for download via the normal channels.
The 1.77 version of PF is distinctly only downloadable via this thread, the specific post in the PF thread and the specific section of my wiki page.
Just to be clear - aside from Planetfall and (Neo)Docklights, none of the OXPs in this thread are compatible with 1.76.1 (although nor are any of them on the table). And for both PF and DL, there are 1.76.1 compatible versions of both which are the ones on the wiki and available for download via the normal channels.
The 1.77 version of PF is distinctly only downloadable via this thread, the specific post in the PF thread and the specific section of my wiki page.
I do understand that, but I did not try to install from this thread (of course, since I'm still on 1.76), I tried to install some OXPs which are labeled as "1.76.1 compatible" in the list on the wiki, such as (checking my dustbin for OXPs with a higher version number than in AddOns) Cabal common library 1.6, Snoopers 2.3.3., BGS A1.5, Vector 1.7.1 and Explorer's Club 1.3.3.
Maybe adding a code "T", meaning "only working in Trunk" to the wiki list would make things clear?
Of course, I could have read the release notes before trying to upgrade, but honestly: who does that, as downgrading what does not work is faster than ploughing through release notes?
Edit: I was indeed on version 1.76, I needed to be on 1.76.1
Last edited by Gimbal Locke on Thu Nov 01, 2012 12:07 am, edited 1 time in total.
None of those OXPs are mine I specifically haven't put any of my 1.77 OXPs on the wiki list to try and prevent the kind of issues you describe.
But yes, I would support either a new column code for trunk, or alternatively if we are having them on the OXP page at all then perhaps a completely distinct table specifically for "special OXPs" such as ones for trunk may be another alternative? Indeed it may be better where there are distinct versions for 1.76.1 and 1.77 of the same OXP (such as the ones listed above, and now also Planetfall and soon to be a couple of others of mine).
perhaps a completely distinct table specifically for "special OXPs" such as ones for trunk may be another alternative? Indeed it may be better where there are distinct versions for 1.76.1 and 1.77 of the same OXP (such as the ones listed above, and now also Planetfall and soon to be a couple of others of mine).
Yes, I think a separate table for Trunk OXPs is a better idea than what I proposed. It would also be less maintenance: once 1.77 gets released it would only take a one-shot merge of both tables.
After reading this thread and seeing screenshots & videos of the new 1.77 OXPs, I want to posit a theorem for consideration: "There exists no upper limit on the awesomeness of Oolite OXPs."
After reading this thread and seeing screenshots & videos of the new 1.77 OXPs, I want to posit a theorem for consideration: "There exists no upper limit on the awesomeness of Oolite OXPs."
Indeed, although there are still upper limits. That said when we do hit them, a quiet word with the devs can often see that particular bar raised out of the way
And to go back to the main topic of this thread - time for another OXP...
Commodities Markets v0.1 splits the main station (and any other station with the role commoditiesMarkets_station) into two parts, one for buying and the other for selling. You select which you want when you enter the screen, and you are then restricted in your trading there. The buying price is slightly increased from normal and the selling one decreased, with the aim to make the trading both a little more realistic and that aspect of the game a little tougher.
Download link is as usual in the first post of this thread, and again this OXP will only work with an up-to-date version of trunk 1.77.
.
![[EliteWiki]](/images/elitewikismall.png){kind=small}
OXP List, the OXPs for 1.77 have a "Y" in the "C" column, erroneously indicating they are compatible with 1.76.1.
I specifically haven't put any of my 1.77 OXPs on the wiki list to try and prevent the kind of issues you describe.
