0.98 problem

[RickRST]

application runs, but when it initialises the tabs, it gets to the bottom and causes a runtime error "PANGO error, unable to create Win32 cairo scaled font. this means out of memory or a cairo/fontconfig/freetype bug... aborting"

Centrino Duo laptop, XP Media centre running WindowBlinds, so probably some non std fonts.

Rick.

[djandruczyk]

application runs, but when it initialises the tabs, it gets to the bottom and causes a runtime error "PANGO error, unable to create Win32 cairo scaled font. this means out of memory or a cairo/fontconfig/freetype bug... aborting"

Centrino Duo laptop, XP Media centre running WindowBlinds, so probably some non std fonts.

Rick.

I've never seen or heard of that error... A quick googling around seems to indicate that you might have stray remnants of an OLD GTK+ release on your system. Do you have GAIM installed? that tends to bring along a semi-private GTK+ release which hoses everything else GTK+ wise on the box.. Uninstalling it usually fixes it..

[RickRST]

No GAIM. Laptop is new, and the only GTK version is the one linked from your site. 0.96 and 0.97 worked fine.

[djandruczyk]

No GAIM. Laptop is new, and the only GTK version is the one linked from your site. 0.96 and 0.97 worked fine.

Nothing changed in 0.9.8 font wise.. The changes include memory leak fixes, and gauge additions for generic polygons..

I'll recheck here, but since I can't duplicate it, it's very hard to find out if it's really a bug or not..

Have you tried multiple times? does it do it before tabs load, after they load, or during loadings? when and under what circumstances can you trigger it?

[RickRST]

I have cured the problem. I simply uninstalled GTK and reinstalled. Perhaps something modified it, although i cannot think what.

The problem occured as the last tab loaded.

Rick.

[RickRST]

another issue.

The tables are all wrong, and the reading for my MAP is wrong too. Does megatunix not retreive the maps from the controller?

[djandruczyk]

another issue.

The tables are all wrong, and the reading for my MAP is wrong too. Does megatunix not retreive the maps from the controller?

"Tables all wrong" tells me next to nothing that can be used to find tye bug. (if it even exists), Which table? VE1,2 or3, Spark 1 or 2, AFR 1 or 2, boost 1, 2 or 3? What is wrong with them? (random data) or offset by some amount? Is it duplicatable?

The sensor maps (coolant temp, mat temp and map pressure) are NOT rettrieveable from the ecu for MS-I firmwares (in MS-II they are).

If MAP is reading wrong it's most likely because you have a 300 or 400KPA sensor and megatunix doesn't know this, so it doesn't know what lookuptable to use. Unfortuantely 300/400KPA sensors were an add on to the firmware and it's impossible for the tuning software to easily detect this and adapt to it.

You can get around it by altering the config files for your ECU firmware.

What firmware are you running so I can give you instructions for modifying the file.

[RickRST]

i am using the 400kPa sensor. The tables which are wrong are the VE1 and Spark 1, which is all i'm using. In Megatune, the bins goto 340kPA, In megatunix, they goto much less, i can't remember off hand. Is this to do with the MAP sensor config too? Firmware is MsExtra hires.

Rick.

[djandruczyk]

i am using the 400kPa sensor. The tables which are wrong are the VE1 and Spark 1, which is all i'm using. In Megatune, the bins goto 340kPA, In megatunix, they goto much less, i can't remember off hand. Is this to do with the MAP sensor config too? Firmware is MsExtra hires.

Rick.

This is due to the MAP sensor. MegaTunix does NOT know how to handle 300/400kpa sensors yet.

[djandruczyk]

i am using the 400kPa sensor. The tables which are wrong are the VE1 and Spark 1, which is all i'm using. In Megatune, the bins goto 340kPA, In megatunix, they goto much less, i can't remember off hand. Is this to do with the MAP sensor config too? Firmware is MsExtra hires.

Rick.

Today I got support for 300 and 400kpa map sensors partially working...

Basically the tables load axis's will display correctly AND update if you change sensor choices. (megatune can NOT do that, without closing MT running mtcfg and changing your sensor choice, and then even so if you pick a different sensor inside of mt for the ecu, the tables scales will NOT update adding to your further MT induced confusion).

The gauges also seem to be working correctly as well too, but since I don't have any real 300 or 400kpa sensors to test against, I can't know for sure. I got the user outputs mapping to track changes in the MAP sensor type as well. The problems remaining to be solved is the 2D-Table highlighters, which get screwed up, and the 3D views, which also got screwed by 300/400kpa sensors, as it screws the pooch in the internal calculations.


NOTE: MT ini's have a bug for AFR tables which display the wrong scales/conversions for MSnS-E series firmwares. As the EGO tab has a algorithm selection that can set the AFR tables to use a SD or Alpha-N mode independently of the fuel/spark tables. To the best of my knowledge megatunix does is CORRECTLY, and megatune does NOT.


Anyone out there, got Linux and a MS with a 300 or 400 KPa MAP sensor? You'd need to use a CVS version to test, and I NEED a tester.

[RickRST]

Maybe worth asking in a new thread? I can only test Windows

Thanks for the continued development

[djandruczyk]

Maybe worth asking in a new thread? I can only test Windows

Thanks for the continued development

Private email sent..

[RickRST]

Thanks for the email

Unfortunetley Windows Live Mail has blocked the attatchment

Could you please forward to richardm79@gmail.com

I have updated my profile to this new address.

Rick.

[djandruczyk]

Thanks for the email

Unfortunetley Windows Live Mail has blocked the attatchment

Could you please forward to richardm79@gmail.com

I have updated my profile to this new address.

Rick.

re-sent