I've Pushed all of my changes to Master, for reference. All the physics settings files are updated as well as the Hover Mods.

Modding Tip:. Finding things in the code is easier if you've set up Windows Search correctly. Right click the Start Button, select Search, put in Indexing Options, then modify to include the target HDD. File types are under the Advanced options and need to include .c, .h, .cpp and .txt files.

Once it finishes indexing, you can search for specific routines and variables inside ANY of the code files just by typing the text into the Windows Search documents box in file explorer.

If you use an ide, like eclipse CDT which is free, you can also use the search facility in that to find anything you need. You can also use ctrl alt H on a function to see what uses it.

What compiler are you using with CDT for EECH? I've been using Watcom so far with no ide.

I still use watcom from the command line. I haven't looked into compiling or debugging in the ide

Ok, thanks. I may try that out, compiling from the ide.

Looks like you never learn, messyhead. All developers was against pushing ECCH code to the open repository, but again you made a decision by yourself and here we are.
To make it clear - I forbid you, or anyone else to push my commits into public repository like GitHub. Am I clear?
Next time you'll want to make such decisions - ask every contributor about their opinion first. That is not childish games.

Excellent. A few years stagnation, finally something moved, and such a #%&*$#.
You really did not write pm to anyone before moving everything to github?

Hey guys, what's the deal? I did a LOT of detective work last year, made several long distance phone calls and determined that the license to the code was totally abandoned back in about 2011. Releasing the code onto GIThub is NOT violating anyone's license. The license was not passed on in any legal venue, it was abandoned. If you have issues with releasing code that you individually worked on, that's your own matter. As I've always understood things, this was a public enterprise and sharing our efforts to improve the sim was what this is all about. I don't expect anyone to ask my permission to distribute the code I've worked on, I expect it to be shared universally for the common good. If you don't like my mods, fine, don't use them. Your choice. If you don't want to share your efforts, fine. Don't upload anything to the server. Keep it to yourself.

This is a great community project with lots of interested players all over the world. Why does placing the code up on GIThub make you mad? Access to make changes is still tightly controlled. Yes, people can look at it, but there has been a copy of the original code up on GIThub for a decade that no one here had anything to do with. It's still there. No one has asked for it to be removed. So what has Messyhead done that violates the community charter to make EECH better that we've all pretty much assumed to be true from the start?

Here's the other version up on GIThub:
Original GIThub Release from 2009.

Learn what?



Evidence?



Where?

A decision had to be made or the access to the repo would have been lost. I'm happy to set up a paid repo if we can get some concrete funding in place for it. I'm not funding it alone.



Feel free to uncommit all of your changes to the code, and push again to master, and we can declare the code dead. Also, just so you know, there has been a github repo for the code created by someone else quite some time before I did, and it contains your commits. Feel free to contact and forbid them while you're at it.

https://github.com/clach04/eech/commits/master



What does that mean?

Just to add, why??

Why not just allow those that want to work on the code and add improvements to just get on with it? None of us is profiting from it, and in fact, spending our own personal time on working on mods. So why now come along and forbid use of your mods?

Gee, and I thought this was supposed to be a friendly gentleman's forum, people who liked EECH and wanted to help make it better. There are only a tiny hand full of us working on the sim in the first place. No need to get hot under the collar, don't we all want the same thing? I want EECH to be the premier helicopter sim around, don't you guys?

Agreed.

come on thealx, it's me Xiii,it was my idea mouse zoom (remember?you first mod) hesco and airfields mod, advanced symbology, ka 50 cockpit and dozens of other things that you did. so i think i can take a voice.do not destroy this simulator, it does not make sense.without you work its end eech .
We all love eech and helos.

Hey thealx,

what's wrong here? Why not coming back to EECH? All we want is to make EECH staying alive. Did you mean, that if nobody is working on it for years, it will survive or even play any role in the simulation genre again?

What were your plans for it? Waiting another 3 to 4 years before improving something? I really could not understand you!

Everyone of us had always respected the work you had done for EECH. Without your work Allmods wouldn't even exist. But if you do not have the time or desire to work on it again, should it die?

I don't claim about code itself - change it, copy it, remove, whatever. But history of commits, which is public available now, can be easily linked with my person. In case of 1.15.2/1.16.0 It's not cool but not a tragedy. Now I see some discussions about Hind mod (1.15.4 test version) which can not appear in public, as it may put me in danger. If anyone will need some stuff from there, code should be copied manually.
For myself, I am continue to move 1.15.4 features to latest release, optimizing and debugging each peace of code. Progress is slow, but hope some day I will finish both Hind and Apache. In such circumstances I can't see the way how it can be pushed to the master, so it will be stand-alone mod if nothing changes.

I agree with keeping the clickable cockpits separate, one of the features of EECH is the ability to jump from one helo to another without having to learn an entirely different set of controls. I like that feature. Clickable cockpits are for ex-pilots and the most serious Sim pilots. I'm a more casual gamer.

I don't know how modding could get you in trouble, but I'll take you're word on that. Safe travels.

It was never my intention to cause problems for anyone. I'll send you a PM so it's not all out on the forum.

Take care thealx,good luck.
Its good idea make separate version for hardcore .
I agree normal eech is great fun and easy for casual players.
But if thealx give permission, it would be great to put the gunner cockpit mi24 in 1.16.clean cockpit,without switches.

I've looked at the clickable cockpit code, it's really complicated. The best way to import the model would be for someone to load the model along with all of the switches and movable pieces into Lightwave all at once, then export the whole thing in one piece, then rename it so it matches the original, with the same subobjects as the original, MFD, needles, etc. Just my observation.

Keeping all the little moving parts would mean keeping all the animations, and a complicated rendering routine. Combining all of that into one model would make it much simpler to work with.