NefMoto

Hi,
Help me please. I need DAMOS + HEX any Audi engine 4.2
I can not find KRKTE: (

I am also interested, did you have any luck with this?

I have an extensive map pack I've made for this, pm me!

Why not just post it?

Choice :)

Kinda pointless, since anybody you give it to can post it.

He just wants to sell it.

Ah. That old retarded game. "I can't post it because I bought it".

LOL. What an idiotic mentality.

He sent it to me without asking for anything in return.

I don't want to sell it, I just prefer to work together with anyone else on this one that's all. There was no buying involved at all. I made it from other ME7.1 damos and time. Retarded is assuming jeesh.

I was talking about the buyer being retarded, not the seller :)

Still, I don't fully understand what is going on. There is something about the tuning culture I still can't wrap my head around.

Ah lol

Yeah you'll never understand the tuning culture, even I haven't worked it out fully and I've been about a bit.

I started the s4 wiki in an attempt to change things for the better, and I'm still trying very hard to eliminate the bizarre glass bead trading games that just encouraged irrational behavior and very inefficient and pervasive wheel reinvention. Thankfully Tony agreed with my philosophy when he started this site.

I see there are still some pockets of resistance.

Money will always make the world go round regardless and those making their living from it will always see it from a different perspective, after all it does pay well

I don't see the incentive to keeping something private just because you paid for it. The concept baffles me.

The whole idiotic glass bead trading game held back 2.7t development an entire decade.

BTW it is just the euro tuning culture, IMO

Pretty much all other DIY cultures (including non-car related) aren't nearly as pathological.

Didn't pay for anything again I'll say!

Make things and don't intend posting anything unfinished online.

That basically stops other people from contributing or worst case someone will start the same thing and you will have two separate guys working on the same thing. There has been several examples on this forum when someone posted unfinished work and other people joined in just for fun and it turned out really good.

There are various views on this for sure and people will never always agree, I'm sure there are other things that I don't mind sharing, personal projects like this one I'm not posting online, unfinished work I prefer to finish :)

Fair enough, especially since there is no really good collaborative way to develop .kp or .ols files (since they are binary only)

at least with .xdfs you can keep them in a source repository...

The only thing i'm missing is a way to convert .xdf back to .kp.. I have yet to be able to synthesize a functioning .kp image w/o winols. I started to make an ASAP/A2L writer to use that as an intermediate format (to import into winols so it can be exported as .kp), but it is a pretty big job.

I find it quite tedious because I use winols to create my initial definition then have to RECREATE everything in xdf so I can actually make changes in tunerpro (demo version of winols)

ECUxPlot comes with a .kp to .xdf converter...

I've thought more about this and I should elaborate on my view to help.

I don't mind working with people in pm who can contact me and be polite(The current N249 thread on here for example). In the past I have helped people who demand your help and aren't respectful of any time spent doing it so it has made me cautious. Plus there are those who never contribute anything.
I've spent far too long doing research, some of it not protected as I asked others. Classic example the MPPS ME7 write routine is fast from my idea checking the sum of each block to see if to write or skip.
There are two views to everything but I like to sit on the fence a little :)

really? I didnt even know that  ::) which version and does it work under linux fine?

mapdump

I thought it (kp converter) only worked with super old kp's for now?

x2

Yes, unfortunately.

I could use some help in extending it, even if it was just some documentation that outlined the format in the version that people wanted to see.

reverse engineering the .kp format is a huge pain, and obviously EVC has no interest in documenting it, since they're a bunch of fucking asshats.

Just sent you a PM  :)

Thanks

Nye:

What do you need, exactly? While I know next to nothing about software development, I have friends that specialize in it. If you can give me a coherent list of requirements, I'm sure I could get it done. Delegation is my superpower.

heh. basically, get winols (the version we want to support) and keep exporting various lists of .kps until i have the whole format documented (or at least the parts that i need)

alternately, somebody could take a peek at my .kp parser and start by documenting THAT .kp format using my parser (yes its a pretty fugly hack) as a guide.

then, with that as a start, try to figure out what the differences are between that and the version we want to support.

If somebody comes up with the format of the .kp, i can adjust my .kp parser to match that spec.

Even if it isn't exact, getting a rough start would be very good.

I can export KP's for version 1.81, 2.24, and 3.46 ATM. You just want me to post a pile of KP's, exported as various versions, I can do that anytime.

so then mapdump wont work on my ols files I have been creating?

well, it is a bit harder than that. Sometimes i'm looking for a specific thing.. say, where is the "signed" bit for the y axis descriptor, and i'll export two versions of the same map, then use a hex editor to find the bit that flipped. So it is really more interactive. it is really time consuming and i could use some help doing it..

it really isn't difficult, just kinda menial.