Curse of the Azure Bonds – build 1.1.7 released

Version 1.1.7 of Curse of the Azure Bonds is now up on the Google Code project site (just the Windows build again).

Fixed in this version:

  • Issue 43, multi-class HP mis-calculated
  • Issue 65, notes a few crashes, one related to SpellConfusion is now fixed
  • Issue 66, fixed attacks (missile,spells) going through walls
  • Fixed bug the you cannot modify stats of characters, introduced in 1.1.6 refactoring

Any issues found, post them here in the comments, email me directly (simeon.pilgrim@gmail.com), or post on the issue list.

Curse of the Azure Bonds – build 1.1.6 released

Version 1.1.6 of Curse of the Azure Bonds is now up on the Google Code project site (just the Windows build again).
Fixed in this version:

  •  Issue 62 , Fixed crash in coin drop code, if you pressed return on empty input, and other fix-ups related to number input
  • Fixed issue with player name input/saving
  • Fixed crash in quick combat
  • Fixed crash with ResistCold and ResistFire spell

Any issues found, post them here in the comments, email me directly (simeon.pilgrim@gmail.com), or post on the issue list.

Playing with Node.js and jQuery

I’ve been experimenting at work. Using Node.js to make a very simple web back-end and using jQuery/javascript on the client side. For work it’s to test out idea’s for “web based product configurations” stuff.

But I’ve been re-purposing the code/lessons at night:

Asm webview
Asm webview

I’ve made those two parts as panels and you can scroll (arrow keys) up/down though the assembly lines (plan to link highlighting when there are more views) and the function details is auto populating and dynamic, and it’s ajax’ed back to the node.js server, and persisted to disk.

Small starts, but I’ve found a “framework” in which to explore some idea’s I’ve struggled how to UI for years, so am over the moon with how this is progressing.

The bonus: the resulting tooling is web based so collaboration is baked in…

Nikon Star Eater - Solved

A while back I posted some sample images, based on service mode on my D5100, and it was noticed that the mode we called Overscan (because it shows the dark pixels of the image) also had the Nikon Star Eater filter turned off.

I released a patch that turned overscan on for the D5100, but the black area makes the processing of the images ugly, and I never released it beyond that as it didn’t seem like a good end goal.

I have today tracked all the code paths down to find the two that turn the Star Eater filter on/off for over scan photo and/or when the exposure is longer than 1/5 second.

After some testing where I was getting confused with default exposure setting of RawDigger, I can verify it works.

NEF files, of 10 second exposures, showing it working as compared to the overscan mode and compared to orignal firmware https://simeonpilgrim.com/photos/nikon_star_eater_samples.zip

I expect this will be released to the BETA firmware patch tool sometime this weekend after more testing is done by the core team, but I would be interested in what Models astro people are keen for this on (no promises), I’ve got the D5100,D7000 done, but other models look “the same” albeit a touch different.

Next Astro features in the “to be done” list, is trying to remove the ~1.4 multipliers on the Red/Blue channels, and removing the black pixel = 0 adjustments also made.

SVN Update Conflict finder

I just discovered a feature I’d never seen before in the Tortoise SVN Client, I did a update from my work repository, knowing there were a large number of project file changes that would conflict.

Normally I would scroll through list of changes and just visually locate the red lines.

Tortise SVN Next Conflict
Tortise SVN Next Conflict

But lo and behold, there is a button that takes you to the next conflict, magic!

RANT: House Costs

Arrrg, National and Labour are arguing about first time home buyers, and it’s driving me nuts.

I’m reading some good posts from NZ econ people, which frame it nicely in econ speak, but it’s just so simple in my mind.

If you want first time buyers to get cheap houses, all house must be cheaper, so that there are cheap houses for them to buy.

I will now make up some numbers:

  • 60% of the population owns houses (group A)
  • 15% of the population wants to own houses but don’t because they are too expensive (group B)
  • 25% of the population don’t own houses because they understand the can’t afford them (and are not bothered) or they want the flexibility of renting. (group C)

So with these made up numbers in mind, we have the two main political parties frothing at the mouth because group B can’t buy houses, and its always been their dream.

Queue sad story of dreams here…. I dream to… oh dreams of the group B people, anyway we all have dreams, work towards them and realise you can’t have it all. Because I have lots of dreams, and so far I’ve not been to the moon!

So to me the “first home buyers” argument is really group A needs to lose some of their capital wealth in their houses to help bring all house prices down, so group B can have cheap houses. How has the big drop in house prices worked for the USA so far???

So which party would be stupid to ask the majority of the country to lose money now and forever, so that another group can get a house. None, they don’t talk about it in this frame of reference, but they are one and the same to me.

How would we go about destroying that value group A thinks they have: be that with tax (first time buyers grants, government houses for cheap, etc) or allowing faster building of houses, or destroying the markets desire for NZ property, you know act ‘North Korea like’ until the world is scared of us. Ether way “The Answer” is going to be unpopular.

National’s solutions seems to be a non-solution solution, but a political “response”.

What I don’t understand is why did Labour start playing this debate/issue.

There are the core base in the Labour camp, who will vote Labour ether way? Are they trying to rev them up, and get them to mobilise the swing voters? Are they trying to win the hearts of the swing voters, the group B people might like the idea of cheaper houses, but as soon as they own a house they will want to increase in value, thus become group A, and not want this policy again. Or the group A people that “have a heart” but are too slow see what this would “require to fix” or is Labour also not really caring about the issue at all, and just trying to make National demonstrate has “no heart for the poor”

I say this as swing voter, that’s not found of National’s sell it all policy, because how well did the Toll Rail  sell/buy back program work out? So now there’s no way I can vote for Labour with a stupid policy stance like this, so I’m back to National, thank Labour.

It all drives me nuts, mix in the NSA spy electronic crap, and NZ rolling over for trade agreements, Labour of all people lowering the drinking age, to vote buying (n years ago) because 18 year olds are “adults”, yet also insisting we need more/tighter tobacco/drink/drug control because those aforementioned adults need to be told how to live (long live the nanny state).

Mean while the politicians embarrass themselves and our country with their antic’s in the “debate” chamber, and around the country. What a bunch of clowns.

And there lies the rub, I don’t trust them to do a mediocre job, I’m not sure how to make them be less stupid, so do I shut-up take my lumps, or join them. Sigh….

Live View Silent Raw on D7000

The D5100 had a string “A:\\LvRaw  .raw” that I notice soon after first decoding the firmware files. I could never fulling put together the how and why of what the code was doing (looking in Task 30 of the D5100 firmware or @0x1AC268 of v1.01 firmware)

After the Magic Lantern guys announced RAW movies and it becoming a hot topic I doubled my efforts to work out how the code worked. But still it evaded me.

Then I bricked my D5100 and I stop working on the project for a month as I’d lost my mojo. Also my replacement D7000 was pretty much all a man could need. But that elusive RAW video mode the Magic Lantern guys have was a very shinny target.

So reading the D7000 firmware with more vigor I discovered why the D5100 didn’t make sense, Nikon had removed the liveview raw saving code, because it’s present in the D7000, and with a simple tweak I got it working.

So for now it’s truly the raw buffer (the part that’s put in the .NEF but with none of the EXIF data), and it takes a hack to turn on, and I’ve not nailed the FPS, nor do I have a clue how to speed it up, but it’s all very cool.

Form the two test video’s I’ve done, the first took 25 frames in 18 seconds so 1.33 fps, on an Extreme 45MB/s San Disk SD card. The second video with an Extreme Pro 95MB/s San Disk SD card, I got 15 frames in 10 seconds, so 1.5 fps. Not ground breaking stuff, but the code to do this was already present in the D7000 firmware. So making it “better” will take a while.

I’ll post a couple of files in case anybody is keen to try decode them. https://simeonpilgrim.com/files/Liveview_silent.zip

Turns out that after some data review, the files contents appear to be the left over ram from taking previous pictures and not the current raw buffer. sigh. Well at least we now how a button, that is wired up to run in live view and a complete understanding of the file handling process, albeit a slow process.

Wheel of Time - Completed

Ah, it only took ~15 years, but I have now completed the series. What started out as a racing set of books, then slowed into a crawl for book ~8, 9, 10, 11 and turned back into a racy  adventure by book 12 and was a full on blood bath with plots getting sorted rather fast and furious in the final book 14.

Quite pleased how it went. Glad some main characters died. Over all very pleased.

I didn’t get much else done in the last month, so now I am free to enjoy other things, and am currently having the ‘completer type’ sense of done-ness about the whole thing.

Thanks Jo for getting me into the books and lending the early ones to me, and thanks Harvey for lending/giving the latter ones to me. Much appreciated to the both of you.

Petrol Price Math

For the last couple of weeks I’ve filled up at the same petrol station, and then entered the details into Gas Cubby and the docket price is 2 cents different from that displayed on the ipod….

Fuel Docket
Fuel Docket

2.119 x 27.94 = 59.20486, which should round to 55.20

I could forgive 55.21, but really 50.22, that’s magic rounding, or they are using more decimal places than shown.

To make the checking easy I’ll assume infinite precision and thus the rounding will trend towards .5 of the last digit. 2.1195 x 27.9405 = 59.2198898 thus 59.22, so it could be both figures are misrepresented or just the $/litre, as when you don’t fudge the price and only the litre amount the total rounds to 59.21.

Or maybe they  just have bad programmers and the company is not evil.

Which reminds me of how my TelstraClear (now Vodaphone) bill never added up. If you telly the sub totals reported to 2 decimal places, the total was off 1 to 2 cents every bill. Scary was that two of three sections were fixed price, and the third was fractional. So how they did that I was never sure.

Bricked My Camera

Sigh, I loaded my first altered firmware on my trusty D5100 on the 25th November 2011, and my last on 22nd May 2013.

Strangely enough we are not sure what was wrong with the patch, weather the area we put the code in was not truly free space,  or if the area we were putting data in was not spare, if the jump to the new code was wrong, was the return wrong, was there an error in the code, or did we take to long and a watchdog triggered.

[Edit 7 July 2013] Hi Nikonrumor people, the problem with the patch was an incorrect sequence of assembly instructions used, and it was a development test patch. So “released” patches are much more “safer” but there is still a real albeit small risk.[Edit]

It’s hard to know but the camera doesn’t boot anymore. The led doesn’t even flash when you put batteries in/out.

So now I get to buy myself a new camera, it’s a little frustrating, as the project had been getting donations, but we had not gotten enough for a D5100 body yet and my plan was to get one for one of the other developers, so we could speed up testing time, and spread the risk. The other guys have different models so are not directly applicable at this “but how does it all work’ stage. And because I started the project we were focusing on the D5100 model as it was the most understood.

If my camera was damaged and I could claim insurance, I wouldn’t get a replacement D5100, I’d likely step up a model, not because I’d out grown the D5100, it’s a fantastic camera, it’s just I’m prepared to spend a little more to get more, compared to when I brought my first DSLR. But getting a D5100 makes the most sense as that’s the model we know the most about from a team perspective.

I rang the Nikon Service centre and it will cost 50% of the new camera price to replace the mainboard. And you can buy replacement off ebay for half that again, but I’m not a hardware guy. They plan is to send the body to a team member and see if they can get the JTAG link working to force reprogram it.

Michaela joked that I should dump Nikon and go with Canon, because of ‘disgust with a camera that’s so easy to break’. She took the news better than I expected.

So ignoring the Canon joke, I’m torn between personal camera needs/wants, and project team needs, and I’m wondering if there’s any community opinion, and if the community is willing to help fund that opinion in anyway?

I’ve previously not directly asked for money for camera bodies, as I didn’t want to ask before having something to show, and I felt we could stop at anytime without feeling a huge sense of dept to the community. So I’m keen to understand what people think.

By the way, we have been able to partially dump the D7100 and it’s ARM based verse Fujitsu FR based and uses a different OS. So the newest camera’s are a whole different kettle of fish, but should be easier to work with, as there is more ARM based disassembly tools.