apache avionics is incomplete. mi 24 gunner clickable avionics incomplete.This is probably the two most important reasons.
Also unspecified slowdown game.

Clickable cockpits can be disabled, and there's key mapping for the gunner cockpit.

Fair enough Apache avionics is incomplete, bit what's there is good.

I'm not sure what you mean? Why would their work be getting put in the garbage?

As it stands, their work from 1.15.4 has been binned as 1.16 doesn't include it.

And just to clarify, 1.15.4 wouldn't be getting released as is. It would be used as the next version, but with other fixes applied e.g unspecified slowdown

ok sorry i deleted my posts probably google translator sucks,And this is a misunderstanding

Yes, let's keep it friendly.

But this shows the problem with the eech mods. There's no plan for what gets done....


Hmmm, that gives me an idea...

Viper1970, it's unfair to compare versions such way - you named cons of the 1.16 and pros of 1.15.4. If you will do vise-versa, you will discover that 1.15.4 not so cool (don't forget you don't know about, at least, half of the problems of this experimental version).

1.15.4 can't be used as master because:
a) two years ago it was untested and unfinished
b) now it untested, unfinished and outdated

there is only one way to move all features to the stable release:

Manually copy code of 2-3 features into master -> improve the code (as I am #%&*$# programmer) -> release test version -> fix reported issues -> release minor update
it will require about 5-10 releases for sure, Mi-24 and Ah-64D will be last in this row. I can do that, but not now - can start November/December best case. Someone else can do that, but only for some common features like lights etc. I can't imagine that my mess, related to cockpits avionics, can be read by any other person.

Btw, you mention about tail rotor damage so often. I already advice you to edit collision object or just replace it with empty.eeo, it will solve related issues.

Thanks thealx. Going backwards to 1.15.4 didn't feel like the right thing, but I wasn't sure how much work there would be to fix that version and merge in the 1.16 changes.

Your suggestion fits in with the roadmap I posted, so we should stick to that, and bring the 1.15.4 features over to 1.16.

Hello thealx,

I don't want to be unfair. I just see things and look for an easy solution. Yes, I never had the time to get real deep into Allmods, because of my freelance work I had back those days. There maybe troubles I don't know of, because I didn't realize them in this few time I had with EECH to fly.

My thinking first was only to grab the "cockpit stuff" and put it to 1.16.0, but as I've seen how much work the cockpits are I thought about doing it the other way arround, grabbing the improvements from 1.16.0 and put it into 1.15.4.

For me this has nothing to do with who made what, only how can we make the most efficient with less work. I have the fear that if we didn't manage it to come further in a relatively quick way, most people will again loose the interest on EECH Allmods and that is what I really don't want.

Even those guys who made Allmods what it is today, lost the interest on it and that's why I didn't thought I could flame someone's work if I suggest to use different parts of different versions if this helps to bring the whole project further. I'm always thinking of a community as a kind of a big family. I really respect the work of each guy who was involved in this project over the years and that's also the reason I could not understand how even those people could watch their remarkable work they have done over so many years, going to the graveyard. My motivation was to avoid this and bring this project back to life again.

I also did'nt want to make my own work the one that is included in a next release. That's not my intention, but as I was one of the loudest who screamed that we have to do something to bring Allmods back to life, I thought that its also my commitment to contribute something to this project. I'm not the guy who wants to take center and never was it, but I've watched Allmods since years and noticed that no-one didn't care of it since more than one and a half year. Not even a small bugfix this whole time.

I'm 47 now and doing flight simulation since I'm 15 years old (started on my dad's factory terminal back those days ) and I have seen so many good mods going to the graveyard over the years, so I decided to do all I can therewith EECH Allmods will not share the same fate. Its an outstanding mod and it is also the only attack helicopter simulation besides DCS, so I think its worth really every effort to keep it alive.

For me it's o.k. if I can stay in the background and others with more experience make the decisions. I have enough work to bring my own project (my home cockpit) to reality, so actually I have not much time for another big project. I will do some work at the EECH cockpits for my own use if I can spent time for it and will post the results (screenshots) here from time to time. If someone is interested in my work, I will share this with the community of course, but I don't want to bring a chaos to this project

I think you're enthusiasm to get things moving has been the driving force behind getting some more work started again on this sim. You can consider yourself a modder now, as you have altered and improved things in the game already.

Thealx was closer to what was happening in the code around 1.15.4 and 1.16, and worked with Firebird, so I was waiting to hear what he thought.

It doesn't mean your work won't be included, in fact it most likely will be, as I'd taken your textures to use with the Havoc instruments fix.

This wasn't the only reason. Yes, as said before I also have an interest that the project comes to a more finished state, because its one of the main software parts of my cockpit. But its also the only attack helicopter simulation we have at the moment and that was why I thought that other people may also have an interest that Allmod keeps alive or at least gets a little bit more finished state.

I think everyone who loves combat simulation and is a little bit a "rotorhead" has an interest that EECH Allmods isn't dying, because of the uniqueness it has. And I tried to help also with my own work to make the project getting more finished but I do not have all the knowledge.

I have to decide if I want to leave my other project for Allmods, because if I make the decision to help modding and fixing it I have to learn really a lot, or only make some smaller things I'm able to do in a relatively professional way. Sadly I'm a perfectionist and if I could not make things the way I like them to be, I want give up. This means that I will spent so much time at it, that the other project comes to a total hold.

I also said that I will do work which no-one other would like to do, if I'm able to do so e.g. textures that have to be revised or text that have to be written, because I know that I also have to bring my contribution to the project. I don't like people who ask for new stuff and do not bring anything by themselfs to the project either.

I'm at the KA-50 cockpit at the moment, but as blackshark also started with it I don't want to make a competing project. And my work takes time, because of my other project and my worse knowledge, but if I decide to share it I would like to have it in an acceptable state, even if I'm a beginner. I think its not very reasonable If you have to wait for me finishing my work or have to finish it by yourself, because I'm not able to do so (Havoc Cockpit)

But I'm still learning and believe me I'm still infected with the modding virus