Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/04/22 in all areas

  1. ... and the moment we get those we can update the sound set.
    6 points
  2. Ok, so here's the thing: The whole deal with CCM's mod being pulled down over "copyright violation" has left me with a bad taste in my mouth. It is simply horrendous business management, to be aggressive that way about whatever rules might have been broken. Sure, the files being distributed on the mod were technically protected by copyright terms. But in practice, where it really matters, there is really nothing that could be done with those files that could in any imaginable way result in lost revenue or damages to Aerosoft. Yet measurable damages can already be seen from the aftermath of said mod's removal. Aerosoft is now an item of boycott to many a disgruntled customer, let alone our individual future purchases being written off, rest assured that whenever the question of whether or not to buy an AS product comes up, our suggestions will be something in the theme of "don't buy those guys' stuff, they're evil". What a way to shoot yourself in the foot. Now, I'm gonna pull rank here and put forward some kind advice as a fellow flight simulation developer. (not affiliated with MSFS, for clarity) In my daily job, we go to ridiculous lengths to make our game as freely moddable as it can ever be. Mods are to be encouraged, and facilitated to the best of our capability. We'll even go to the trouble of making ourselves available all day on our Discord for modders to ask us whatever they need help with. This strongly pro-modding attitude has proven immensely beneficial in the past. See: I'm sure you're familiar with a game called "Kerbal Space Program". Well, my twin brother and current employer was the original lead developer of that game. Back in the early days I was personally volunteered as chief community admin in those forums and even got to write down the original guidelines for addon publishing, which remain mostly unchanged by the admins that followed after and continue to this day (at least I hope so) Having put modding friendliness as a first-and-foremost prerogative was undoubtedly a critical move leading up to the game's ultimate popularity. Therefore, it pains me on more than one level to see fellow developers of simulation products I'm personally interested in, doing such wild acts of lunacy as going against a modder over some copyright technicality that effectively hurts nobody in practice; While to pursue it thus clearly makes for the worst PR move imaginable. Now, it would still be a very welcome turn of events and a most satisfactory surprise if in light of this, AS were to change their stance and allow the mod, despite it being technically against the rules. This also applies to the previous case of Mugz mods for the CRJ. Sometimes, rules get in the way of a greater good. Would you blame a driver for breaking the local speed limit in order to reach help quickly and save a life? No, you give them sirens and paint "ambulance" on the side of their vehicles so they can do that very thing more effectively. There's a lesson here somewhere, I hope you can see it.
    6 points
  3. As was left unanswered in the CRJ thread: >> So the liveries are coming down too? The config files they contain are not in the paint kit. The instructions in the paint kit do not grant permission to redistribute specific configs. Therefore if it all falls under the same blanket agreement they should not be allowed to remain. Much of what the community is frustrated and confused about here centers around highly selective enforcement of a policy which removed one set of mods with no user-discernable difference from the multitude of other similar mods which remain available. From where we're sitting, the only difference is that the removed mod changed aircraft behavior which some feel is incorrect, while those that remain could not possibly be construed as critical of the base product. "This CRJ mod is just a panel.cfg and therefore not considered to be actual code. From my perspective as the author of the original file, that's fine." - Hans Hartmann, CRJ thread. Which .cfg files are just a .cfg and which are "actual code"? Is an xml file "actual code"? If parts of the package are protected and other parts are not, there must be transparency. Mods of panel.cfg are ok? The livery mods contain aircraft.cfg, texture.cfg, and model.cfg; are those OK? Is flight_model.cfg and ai.cfg somehow not OK if all of the above are? Either let people participate in an ecosystem of mods, enforce this Copyright-alleged takedown universally, or provide clarity. Every time someone has asked "which file was the problem" the response has been "all the files are protected".
    5 points
  4. There is / was a very good mod for the Twin Otter on flightsim.to ("CCM’S Twin Otter mod”) fixing bugs and improving flight model and sound. Unfortunately Aerosoft have asked flightsim.to to remove CanadianCaptainMoustache's mod. This is really bad style. The sim is living from all the phantastic mods we get from gifted flightsim enthusiasts and CCM's mod kept the Twin Otter enjoyable for me despite the initial bugs and problems. When Aerosoft refuses to accept mods for their aircraft this will have been the last product from Aerosoft for me. Hope they will think about this position.
    5 points
  5. If it’s such a clear copyright violation, then why do other commercial developers openly allow their aircraft to be modded in the same way? What material harm is being done to Aerosoft by distributing a free mod that requires the paid product to function and is it worse than the damage Aerosoft is doing to its enthusiast customers?
    4 points
  6. It cannot be said with any certainty that any laws were being broken. Copyright law is very fuzzy around edges such as these, it is a problem typical of our generation (e.g: YouTube vs. Everyone in it) What can be agreed with is that a company policy was claimed as having been violated. That is not the same thing as a law. Nor does the claim substitute for a canonical fact. No other publisher (apart from that one we don't speak of) appears to have any issues whatsoever with the publication of modded .cfg files, regardless of what's in them and how much was changed. That alone clearly indicates that nothing done here was ever in breach of any official legislation. We're talking about company-specific rules which were laid out somewhere between AeroSoft and whoever else is involved. So currently what we have is: AS demands that end users jump through unreasonably convoluted hoops in order to install a mod that, with any other publisher, would've been a drag-and-drop operation. Also they demand that developers go through immense efforts to package these mods and document their installation, greatly increasing the technical skill required of a hobbyist modder, to achieve results which others make easy. That is not what I'd call "encourage and welcome". Maybe if a specialized tool were provided to expedite these unusual requirements, then perhaps it would be fine. But as of now, it remains an unreasonable barrier to enforce. I would suggest it'd be much simpler to rethink those company rules It'd be in everyone's best interests to do so. Think about how every mod posting out there is a free ad banner for your product.
    4 points
  7. " "The uploader (again he prefers to remain anonymous even though I told him we are in no way seeking legal actions, just a correction on the files), reacted rather unexpectedly and told me he would share this with everybody. Most people who violate a law do not do this. It was clear he simply was not willing to respect copyrights. He felt it was in his right to share the files because they contained bugs. We, respectfully, disagree with that." If we're going to start by utterly making things up, I have zero input into this.
    4 points
  8. I bought the Twin Otter so I could fly my favorite aircraft. You've taken away the mods that made it acceptable. You made your payware is completely useless to me. I've uninstalled it and I will NEVER fly it again. I'll never buy any of your products again, and I'll tell everyone I know at every opportunity and on every forum I can find, to avoid Aerosoft. I want my money back. I want it back, NOW! (Hey, Admins? You might delete this message or you might block further comment. I've saved it to repeatedly repost until I either get my money back, you fix what you've done, or you kick me out of here.)
    4 points
  9. I was going to buy the Otter after seeing the excellent feedback on CCMs mod. I will no longer do so. I understand the legal points made, but this goes against the spirit of the flightsim community and will destroy a key part of what it means to be a flightsimmer.
    4 points
  10. You can enjoy the product and also encourage Aerosoft to stop being hostile to its users. These things are not mutually exclusive. The community has made .cfg mods to planes for years—including the ones from Asobo.
    4 points
  11. I agree. This is simply appalling, anti-community behaviour by Aerosoft. I won't be buying an Aerosoft product again, after the rushed poor quality release of the Twin Otter, but much more because of this unbelievable behaviour. Goodbye, Aerosoft.
    4 points
  12. I agree, a very bad move from Aerosoft. If the aircraft was ok to start with I wouldn't have to buy a sound pack to be happy with it. But I'm OK with that. But going after people who make mods? Shame on you.
    4 points
  13. Then make the changes yourselves like you should have done ages ago. The fact that someone can quickly create these important fixes by changing a few lines of text shows that you are not dedicated to making a quality product.
    4 points
  14. Yes, What we have here is really not all that difficult a problem to work out, when isolated from the insults and accusations. The FlightSim community has developed over the course of many decades, a number of reasonable implicit expectations for what they should or not be allowed to do when modding. The general consensus is that "As long as a mod doesn't circumvent the need for a purchase, it should be fine to publish it". This is NOT against the law, in fact, most likely the massive amount of addons published under these terms sets a significant precedent to uphold these expectations under the terms of Fair Use. Anything short of that, is construed by the crowd as excessively restrictive, then the Fighting Words start flying. AeroSoft is therefore at a make-or-break position, having been put there by whatever circumstances of their own making or not, doesn't matter. The critical item in question is whether or not AS can somehow get their internal politics sorted out in a way that allows them to give the community what 40 years of FlightSim have had it expect, that is: The right to freely publish any mods that don't contain enough data to enable an avenue for piracy. Anything else is merely noise besides that one key point. That's what we ask of MK, which is indeed quite a tall order, but that's a manager's job. To bang together whatever heads need banging to get them to agree on something that is a clear benefit to everyone involved. And on this hinges the company's entire reputation. Truly, if he pulls that rabbit out of the hat, AS goes immediately from villain to hero in this story. The alternative is a bit grim, though.... Let's all think of bunnies instead.
    3 points
  15. The solution is so easy, and it should be staring everyone in the face. Aerosoft gives permission (Grants a shared copyright - or whatever you want to call it) to CCM mod of a specific set of .cfg file to the Twotter, and going forward, BOTH entities have copyright ownership of the resulting work product, as derived from that version. The current and future owners of the Twotter are Happy Aerosoft are happy, they still hold, copyright (ie Their copyrights remain PROTECTED) CCM is happy, he can distribute his MOD, - and any modifications to that MOD based on their joint Copyright of future derived works , that he spent time & effort creating, and I believe is more than happy for Aerosoft to use any of his MOD in future Twotters, which I believe was his original hope, when he started the Mod, and offered to work & share it with Aerosoft. EVERYONE wins, everyone “saves face”, Legal is happy, and we all move on in a Positive way …
    3 points
  16. Flight sim community is and was always full of drama. Even as a part of it i think there is nothing to be concerned about, a few weeks and there is another topic everyone is mad about. I mean this topic just got startet (and is still going on) for whataboutism, what in the world?
    3 points
  17. "The community has made .cfg mods to planes for years..." And that's exactly what they made .to take down. Great way to turn a happy vocal customer into a really angry far more vocal one.
    3 points
  18. Just caught up - and that is game over for me buying from Aerosoft. Annoyed me with the CRJ - it still has buttons that used to work and have stopped despite an update. Then with the Otter, shocking sound so bad that I had to buy a sound pack. Its thanks to the community that the Otter is my fav plane because of CCMs mod and I might have considered your next plane because I know the community can make them better thru tweaks. (though I have no interest in your plan for an Airbus) I don't understand the legal argument, what is anyone going to do with the files? What commercial gain? What secret business sensitive info is in there? Have you some code that only you know and have developed that magically make the planes fly so realistically? And from the communities response - there is a cohort of people that do not believe it flies realistically and in the spirit of community have offered an alternative. An alternative that could drive more people to wanting to buy it form you and augment it with a mod. Like certain other developers you do yourselves no favours and you should have expected, like every other developer - that someone will mod the flight dynamics.
    3 points
  19. I agree just as Mods did wonders for kerbal space program, mods MADE that game, the mods and tweaks for the twin otter, brought it from a "below average" addon, to one of the best addons available right now. Im saddened to have lost the ability to fly it the way i came to love it.
    3 points
  20. Have you considered reaching out to CCM and working with him, he has done more for your product than any other content creator out there!
    3 points
  21. Oh my, so many angry posts, but few actually suggest the poster understand the complete issue. I have said all of this before but let me write it one more time, in more detail. I will leave the post open indefinitely, but I do not feel the need to correct misconceptions. Here are the simple facts. I was informed that a file on https://flightsim.to/ contained a huge amount of our copyrighted files. A clear copyright violation. Not a huge deal, we ask for the file to be removed, that is done and normally the person who uploads it (in this case he prefers to remain anonymus) removes the copyrighted files and reuploads it. Happened dozens of times and often I assisted in removing the problematic parts. Never did this end up in a legal territory. Never did we even mention that. Never did we do so in this event! This request was done on behalf of the developers who made those files. As publishers one of our task is to represent the copyrights of people who work with us. That is in the contracts, that is why we take a percentage of the sales. Chris removed the file on my request. The uploader (again he prefers to remain anonymous even though I told him we are in no way seeking legal actions, just a correction on the files), reacted rather unexpectedly and told me he would share this with everybody. Most people who violate a law do not do this. It was clear he simply was not willing to respect copyrights. He felt it was in his right to share the files because they contained bugs. We, respectfully, disagree with that. The uploader responded very confrontative and basically tries to attract more attention to his copyright violation (which might explain why he wants to remains anonymous) Just now I send him (of course I know who he is, but again we have absolutely no intention to start any legal action, in fact I offered him public assistance on this forum on how to make his tweaks public), three simple questions: Why did you seek the confrontation? You very well know what you did was a copyright violation. You know very well that 97% of what you shared is stuff that you did not write. You are not stupid so you know a publisher simply is forced to take action, so you must have expected problems but decided to press on. To make a point? To punish us (me)? You clearly like the product otherwise you would have not gone through all the trouble. Are there bugs to fix? Sure and we are working on those. A lot of what was in your file was corrected in our last update. Some of it because of your kind assistance. Your file contained a bug fix for an issue with the Generator 2 annunciator that we missed but that is now corrected and in the testing pipeline. I will credit you in the readme if you allow me to do so. Why did you not simply remove the whole copyright issue and only publish the changes? You are clever, you know how to use the diff command. You would have achieved the exact same and everybody would be happy. I would even welcome it on our forums! Parts of the file, like the sound tweak, are in no way problematic as they contain none of our code. If you feel the Twin Otter internally should sound like the King Air, fine! As you might have read we are expecting the new sound recordings done on a Twin Otter and hope to fix that nasty issue. Why do you wish to remain anonymous? We have absolutely no intention to go after you for the copyright violation, if you want I will say so publicly. As the file is removed that whole issue is behind us. I just feel a lot more comfortable discussing things in the open. My name is Mathijs Kok, what is yours? If there is any reply and the uploader allows me to share it (he already was offended when I mentioned just his first name), I will add that to this topic. ____________________ Now lets get a few things straight. Does Aerosoft have a problem with flightsim.to? Hell no, we all go there every day to see the great work people do! We have offered our assistance to Chris many times. He knows he can contact me any time, and we’ll be there. What he does for the fs community is fantastic. Does Aerosoft have a problem with tweaks? Nope. You will actually find on many of our manuals that we invite them. Just check. If a customer finds an issue in our software and fixes it, our first response will be to say thanks. Often followed up by a request to contact us to show our appreciation in the form of a freebee or a beer. Are repaints now also considered a copyright violation? Come on, we offer a paint kit, we offer to distribute the files, we make it clear the copyright of the repaint is shared between Aerosoft and the repainter (so neither can sell the liveries, who wants that, right? Why do we not ask to have all tweaks removed? Well, if they do not contain our copyrighted code, why would we? If somebody uploads a file that contains none of our code but changes the behaviour of a product in a way they feel makes it better, great! So how do I share tweaks without violating copyrights? Basically, start with not sharing what you did not type. If you have a tweak to a file, do not share the file (as we have copyrights on that); share what you changed. Every person who makes these changes knows the diff command; it shows you the difference between two files. Say you found a bug in this code: And think it should not be circuit 2, but circuit 1. Simply tell people to edit line 10 and change 2 to 1. You did what you wanted, assist people in fixing an issue (and thank you for that) and you still respected allo copyrights. A post like that would be very welcome on our forum. I personally would upvote your post. Other people can then test it and give there comments. Some tweaks work and others do not. If your tweak does not contain any of our code, say you want to replace the sound.cfg with another one that links the sounds to the King Air, just post it on our forums. We might not believe a King Air sound in any way like a Twin Otter, but if that is what you believe makes the product better, post it! Does not affect our copyrights in any way and is very welcome. So what is a copyright issue? If you make a few changes to a file that is copyrighted and upload the whole file. That is simply a copyright violation. It is illegal. As publisher we have to ask it to be taken offline. If you have any doubts, if you have any question what you should do, just ask me. mathijs.kok@aersosoft.com. By now everybody knows my email, lol. I enjoy interacting with customers even if we disagree. But you are still an asshole! Yes, I had a fair bit of hate mail because of this. I get paid for this. I get paid to protect copyrights and I get paid to take abuse from some people. Most of the emails I got were to the point and while not nice, written with some respect. I replied to those, explaining the issue was simply copyrights etc, see above. I was happy to see that almost all the people responded positive to my comments. As I keep saying, almost all people will listen to arguments if they take the time to read stuff. Read and than comment. Some others where less pleasant. Sign of the times I fear. My favorite today was this one: "Mr kock, whats in a name?????/, you are a funcking moron". A wordplay on my name, how clever! I was temped to tell him I was the lucky one in my family. My fathers was name Ruud Kok (and he and I travelled the US for years) and his brother Dick Kok (and he emigrated to Canada!) but I did not and just clicked 'spam'. _____________________________ As said this topic will be open and will stay open, you are all welcome to share your comments (you are even allowed to make more comments on my name!). Just do not personally offend other people who are not paid to have to deal with this. I will however close all other topics to make sure we all can read each others comments in one topic.
    2 points
  22. no matter the fault or legal situation, what a sad situation to see such degeneration of respect, thought and communication. Not professional at all!
    2 points
  23. I hope you stood on a corner in Winslow, Arizona. It's such a fine sight to see. BTW, drinks with @Heinz Flichtbeil and maybe @pa4tim in Chicago tomorrow or Sunday? Best...
    2 points
  24. Another leg towards the target After thinking back and forth yesterday about our further route planning, we decided today to leave out "St Louis" and fly to Indianapolis. My co-driver "the elephant" would like to take a look at the race track. So we thought about whether we could include Indianapolis and whether that would be achievable for us. The flight plan was put together quickly. And then we're on our way. Today we take off via runway 17L in the direction of Indianapolis. Like last time, our cruising altitude is 11,000 feet. After one hour 12 minutes we reach Springfield and fly over it. We continue towards Saint Louis, which we fly over after 2 hours 15 minutes, we have a good view of the Mississippi River. And already we leave Saint Louis behind and we continue. The landscape is relatively monotonous Fields, fields, in between a few places or farms. Nothing really exciting. The owl, our columnist, is working on her notebook again and writing travel reports. In the meantime, I'm busy with the approach to the airport and prepare myself mentally for the approach. We have received turbulence warnings from Center, but have not been able to detect any. We chose Indianapolis, one of the smaller airports that is close to the racetrack. According to the center's instructions, we begin our descent to 4,000 feet. The approach to runway 21 runs smoothly. Weir touched down gently and we can choose a parking space and park the plane. We do the usual formalities and we're already being slowed down by the authorities. All documents, entry papers are checked. We can forget about the visit to the race track today. The campaign lasts a total of 2 hours. The owl uses the time and books us rooms at the Best Western Plus NW Hotel. She also gets us a rental car that is ready for us at the airport. We check into the hotel. And we look for a restaurant nearby, where we discuss further route planning. Then we visit the hotel bar for a moment and after the drink we go to bed. Ein weiteres Leg dem ziel entgegen Nachdem wir gestern hin und her überlegt haben, wie unsere weitere Streckenplanung aussieht, haben wir heute beschlossen „St Louis“ außen vor zu lassen und nach Indianapolis zu fliegen. Mein Co Pilot „der Elefant“ würde gerne die Rennstrecke angucken. Also haben wir überlegt, ob wir Indianapolis einplanen können und ob das für uns erreichbar ist. Der Flugplan wurde ist schnell zusammengestellt. Und dann sind wir auch schon auf dem Weg. Heute geht es über die Startbahn 17L los in Richtung Indianapolis. Unsere Reiseflughöhe beträgt wie die letzten Male 11000 Fuß. Nach einer Stunde 12Minuten erreichen wir Springfield und überfliegen es. Weiter geht es in Richtung Saint Louis, dass wir nach 2 Stunden 15 Minuten überfliegen, dabei haben wir einen guten Blick auf den Mississippi River. Und schon lassen wir Saint Louis hinter uns und es geht es weiter. Die Landschaft ist relativ eintönig Felder, Felder, zwischendurch ein paar Orte, oder Farmen. Nichts wirklich Aufregendes. Die Eule, unsere Kolumnistin beackert wieder ihr Notebook und schreibt Reiseberichte. Ich beschäftige mich derweil mit dem Anflug auf den Flughafen und bereite mich Mental auf den Anflug vor. Wir haben, von Center Warnungen zu Turbulenzen bekommen, können aber nicht feststellen. Wir haben uns Indianapolis einen der kleineren Flughäfen ausgesucht, der in der Nähe der Rennstrecke liegt. Nach Vorgaben des Centers beginnen wir mit dem Sinkflug auf 4000 Fuß. Der Landeanflug auf die Bahn 21 verläuft ohne Probleme. Wir setzten sanft auf und können uns einen Abstellplatz aussuchen und parken den Flieger. Wir erledigen die üblichen Formalitäten und schon sind werden wir von den Behörden gebremst. Alle Dokumente, Einreispapiere werden geprüft. Den besuch der Rennstrecke heute können wir vergessen. Die Aktion dauert insgesamt 2 Stunden. Die Eule nutzt die Zeit und bucht uns Zimmer im Best Western Plus NW Hotel. Sie besorgt uns auch einen Mietwagen der am Flugplatz für uns bereitsteht. Wir checken ins Hotel ein. Und suchen uns in der Nähe ein Restaurant, dort diskutieren wir über die weitere Routenplanung. Dann besuchen wir kurz die Hotelbar und gehen nach dem Drink ins Bett.
    2 points
  25. Leg 9, 3 march, KELM to CYMX ( 382 nm) Elmira, Binghamton (NY) Rockdale, Saranac lake(NY) , Ottawa, (Quebec, Canada) Montreal (Quebec, Canada) Ready for a test flight Ottawa Montreal After working 2 days on Deety (DC-8) we go up to Canada. Not yet in the DC-8 because it has no sleeping facility (yet). But the test flight went well. We took Dixy instead. When we were almost finished breakfast we heard a strange sound outside. Betty ran to the window and called me to come and look. There was a lot of smoke whirling around some square red box, when the smoke went away it turned out to be a phone boot and a man comes out. What the heck is that, Betty says. I answer, “the only thing I can think of is the Tardis”. And who is that Betty asks, “ Who”, I say. Betty, “The guy coming out the phone boot “. I repeat, Who. Betty reacts a bit irritated, That guy with the long shawl. Who, I say, starting to have problems not to start laughing. The guy, walks to Quty and knocks on the door. Betty opens and he introduces him self as Doctor Who. Betty turns around and sees me laughing. Babe, I told you it was Who. I invite him in. When we are nipping on our tea he starts telling. He found traces of time and dimension shifting and followed them to here. You probably think I am mad but you must believe me , Dr Who say’s. No, I believe you. You use a transvortexincapicitator. How the hell you know that Who replies. Because it is mine design, I say. That is impossible he says. I told hem that he met me years ago while he was working on the first version of the Tardis. Trying to beam objects between dimensions. You were doing experiments but I knew from the future it had some very bad problems and finally would kill you in 2032. So I knocked on your door telling you I was from the cable company. When I was “working” you went to the toilet. I quickly opened the Tardis and..He interrupts me, did you put the designs in the Tardis ? Yep, I say. Then I want to thank you. I tell him to follow me. In the garage I show him the transvortexincapicitator. I show him the details. This version is more developed as the design I gave you. I now can move objects without being in it by using slave units and I can move very big objects if they have a slave unit. Like how big, he asks. You see that DC-6 next to us, the plane with 4 props ? What, are you able to shift that plane ? Yes I say, there are no limitations in size, at least I have not find limits yet. A few days ago I shifted a DC-8 from an other dimension in the 60’ s to this dimension and time. Dr. Who watches me with big eyes, you can shift dimension and time at the same time ?. Yes and now I say, it is complicated but I will show you the schematics. We spend a few hours talking about the details. And he showed us the Tardis. I told him we had to leave and invited him to join us. He would like that but tells me he thinks the Tardis is to heavy to move in the plane. That is not needed, I say. I mount a slave unit in the Tardis and when we arrive we shift it to where we are. During the flight we talked a lot about the transvortexincapicitator design. He too, had made some interesting modifications in the Tardis. He was able to detect transvecterial bifluxgate admittance transients. When it was dinner time I walked to the DC-6 to tell our guests dinner is ready. To my surprise nobody was there. Then I noticed the transvortexincapicitator from the DC-6 was missing. Dr Who ran to his Tardis and came back with his modulating inverseregineratux. After some tuning he told me they had shifted to 1872. Why would he do that Betty asks. I think I know I say. He went back in time to met Phileas Fogg. Does he know he needed to arm the indexial parallelreverser unit here, Dr Who askes. I doubt that Betty answers. We look and it was not set. What we do now Betty asks me. We have two options. We can with the help of Dr. Who follow them, or we can leave it like this. I will contact @pleincrazy, Betty says. Do you have Time, Doctor, I ask. Time is on my site, he sings as answer. Are you a Rolling stones fan I ask. Yes, since they started. he replies.
    2 points
  26. I've been researching the subject, and yes, it all points to it falling under Fair Use Read up: https://en.wikipedia.org/wiki/Fair_use Let's try and examine the "legal case" and its merits by parts: AS claims infringement because: The published file is considered protected by their own copyright terms The file is therefore "theirs" and cannot be redistributed without permission (which isn't given because?...) The Public claims no infringement applies, given that: There is no way in which the published files diminish, detract or undermine AS's revenue due to the mod's publication The mod file cannot be used to reconstitute the final product without prior purchase of the original The modded file is likely an exception to copyrights coverage given Fair Use in the first place Even if not excluded, the modded file can be said to possess Sufficient Change to qualify as an original wok anyways. There is a large amount of Public Interest on the availability of said mod. The mod is not a commercial work and its author derives no financial gains from it. AeroSoft itself has only to benefit from the mod's publication, by added final value to their product as well as extra exposure (every mod posting is a free ad) do I really need to go on here?...
    2 points
  27. How would a customer determine which components of these products are copyrighted and which are not? There is no mark or indication within the files.
    2 points
  28. Agreed. This is appalling behaviour. Strange that Aerosoft apparently didn't stop to consider that virtually all other major developers don't demand that simple performance mods be taken down. I won't be buying Aerosoft again, because an aircraft that can't be modded is a much bigger risk than one from another developer that understands the community.
    2 points
  29. I can confirm the stutters is gone for me after updating to SU8. I also did a reinstall of Nvidia driver 511.79 before updating - so both actions could have solved the problem for me.
    2 points
  30. Heute war ein prächtiger Frühlingstag und ich habe noch Urlaub. Also machte ich einen Ausflug in die Speck, um zu schauen, was da so kreucht und fleucht. Speck heisst der Flugplatz LSZK in Fehraltorf im Zürcher Oberland, der von der Flugsportgruppe Zürcher Oberland betrieben wird. Er liegt 10nm Luftlinie südöstlich von LSZH und 7.5nm von meinem Zuhause entfernt. Von hier aus hatte ich einen optimalen Ausblick auf das Flugfeld. Und zu sehen und fotografieren gab es folgendes: Denney Kitfox Model 4-1200 Ein handlicher Hochdecker-Bausatz, den man einfach zusammenklappt, auf den Anhänger lädt und wieder mit nach Hause nimmt. Jodel DR1050 Piper PA-28-180 Cherokee E Tecnam P2008JC Piper PA-18-150 Super Cub Beechcraft 58 Baron Auch ein Drehflügler war unterwegs. Robinson R44 Raven II Der aufmerksame Beobachter hat die Tragflächenunterseite am oberen Rand dieses Fotos bemerkt. Was nichts anderes bedeutet, als dass ich auch in der Luft war. Während ich so am spotten war, kam einer der ansässigen Fluglehrer auf mich zu und fragte, ob ich Lust hätte auf einen günstigen Rundflug. Er habe einen jungen Flugschüler, der sich seine Flugstunden quasi vom Mund absparen müsse. Und um die Kosten für ihn ein wenig zu senken, könnte ich für CHF 50.- als Passagier mitfliegen. Eine solche Gelegenheit konnte ich mir doch nicht entgehen lassen. Also nichts wie rauf auf die Rückbank der Cessna 172S Skyhawk SP und los. LSZK Speck von oben Blick Richtung Glarner Alpen (leider etwas diesig) Meine eigentliche Hombase Hasenstrick LSPK, weil noch etwas näher an meinem Zuhause als LSZK. Aber seit einigen Jahren nicht in Betrieb wegen Geldstreitigkeiten zwischen dem Grundstücksbesitzer und der Fluggruppe Hasenstrick. Im Landeanflug auf RW30 von LSZK Das war ein etwa 40-minütiger Rundflug über meiner Heimatregion mit dem ich ganz und gar nicht gerechnet hätte. Um so schöner war dieser Tag und ich freue mich schon auf das nächste mal. Denn der Fluglehrer und ich haben unsere Telefonnummern ausgetauscht, falls er mal wieder einen mutigen Passagier benötigt, der sich an der Flugstunde eines Schülers beteiligt. Ich bin auf jeden Fall wieder mit dabei, so lange der Fluglehrer auch mit dabei ist 😄.
    2 points
  31. After spending the night in this super expensive hotel, we treated ourselves to a leisurely breakfast. Of course that wasn't included in the price. After breakfast we made a short detour to the Grand Canyon. From there we planned today's route. We have decided to skip one of our landing stations (Albuquerque) and fly directly to Oklahoma City. The range of our aircraft gives that without further ado. After the start preparations, we then started via runway 21. Due to the altitude, the take-off distance was considerably longer than usual. The flight over the desert-like terrain was not particularly exciting. Since the plane was calm in the air, "the owl" was able to type out a whole series of travel reports. After takeoff from the Grand Canyon, we climbed to our cruising altitude of 15,000 feet. We need this altitude to be able to cross the mountains. Since we didn't plan any other sights for this flight, we stayed at this altitude. It's now 4:30 p.m. and dusk is slowly beginning to set in. The weather conditions are very good, since we flew a bit faster today, we arrive in Oklahoma before dark. Nothing comes of our planned approach, the center assigns us a new approach. But it's not a problem either, since this approach is even easier to carry out than the planned approach. As instructed by Center, we hold course 084 and descend to 5,000 feet. The landing approach is completely unspectacular. After landing we taxi to our parking position. After-flight check Secure the aircraft and the special and usual formalities hold us up a bit. The owl organizes a hotel room during this time. She was then able to get us rooms at the Holiday Inn Express and Suits, Oklahoma City. For dinner we headed to a Mexican restaurant, the Birrierai Diaz. We ate something in the restaurant and discussed the route for the next day. Then we went back to the hotel, had a nightcap at the bar and then went to bed. Nachdem wir die Nacht in diesem super teuren Hotel verbracht haben, gönnten wir uns ein gemütliches Frühstück. Das natürlich nicht im Preis inbegriffen war. Nach dem Frühstück haben wir noch einen kurzen Abstecher zum Grand Canyon gemacht. Dort haben wir die heutige Route geplant. Wir haben beschlossen, eine unserer Landestationen (Albuquerque) ausfallen zu lassen und direkt nach Oklahoma City weiter zu fliegen. Die Reichweite unseres Flugzeugs gibt das ohne weiteres her. Nach den Startvorbereitungen sind wir dann über die Runway 21 gestartet. Aufgrund der Höhe war die Startstrecke erheblich länger als gewohnt. Der Flug über das wüstenartige Gelände war nicht besonders aufregend. Da die Maschine ruhig in der Luft lag, hat „die Eule“ eine ganze Reihe Reiseberichte abtippen können. Wir sind nach dem Start in Grand Canyon auf unsere Reiseflughöhe von 15000 Fuß gestiegen. Diese Flughöhe benötigen wir, um die Gebirge überqueren zu können. Da wir uns für diesen Flug keine weiteren Sehenswürdigkeiten vorgenommen haben sind wir auf dieser Flughöhe geblieben. Mittlerweile haben wir 16:30 Uhr und die Abenddämmerung beginnt langsam. Die Wetterbedingungen sind sehr gut, da wir heute etwas mehr schneller geflogen sind kommen wir auch vor der Dunkelheit in Oklahoma an. Aus unserem geplanten Anflug wird nichts, das Center weist uns einen neuen Anflug zu. Ist aber auch kein Problem, da dieser Anflug noch einfacher durchzuführen ist als der geplante Anflug. Nach Anweisung Center halten wir Kurs 084 und sinken auf 5000 Fuß. Der Landeanflug verläuft vollkommen unspektakulär. Nach der Landung rollen wir zu unserer Parkposition. Nachflugkontrolle Maschine sichern und die Besonderen und üblichen Formalitäten halten uns etwas auf. Die Eule organisiert in dieser Zeit schon mal ein Hotelzimmer. Sie konnte dann für uns Zimmer im „Holiday Inn Express and Suits, Oklahoma City“ bekommen. Zum Abendessen haben wir dann in ein mexikanisches Restaurant angesteuert, das Birrierai Diaz. In dem Restaurant haben wir etwas gegessen und die Route für den nächsten für den nächsten Tag besprochen. Danach sind wir zurück ins Hotel gefahren, Haben dort an der Bar einen Absacker genommen und sind dann ins Bett gegangen.
    2 points
  32. Mainly because we were simply not aware of this file. Thanks for pointing it out. We'll have a look at it and when it contains no copyrighted materials there should be no issue! When it does contain copyrighted material I will discuss it with the person(s) who created it.
    2 points
  33. no one is ignoring it, its amazing how your the only addon develeloper in all of flightsim to "have to legally" push this issue
    2 points
  34. @Mathijs Kok Modifying .cfg files has been part of the flight sim community for ages. I understand you want to protect your product but your approach to this issue does come across a bit aggressive. CCM reach out to Aerosoft on multiple occasion and share his observation on your aircraft and request Aerosoft to make thoses changes. You have chosen to ignore his comments. He just decided to make some properties changes and wanted to share with the rest of the community. Can we stop hiding behind legal bullshit and let the community enjoy a product they have bought ? It's clear that Aerosoft has decided that wanted the aircraft to remain arcady and unrealistic. This is the demographic target you want for your product. Why stop the rest of the community who has paid for your product to make it more to their liking ?
    2 points
  35. More than Aerosoft themselves. All they did with the latest patches were minor adjustments nobody asked for. Now fixing the major wildfire that the sounds or the flightmodel are. Nothing. This is my final comment here. Not buying a single 3 dollar addon if it says aerosoft on it. Not even if I want it. Too bad.
    2 points
  36. I did and it's not "dumping your code for free". Anybody who buys the Twin Otter from your website has access to this file and the code contained within it. This mod is made for people who own the Twin Otter, therefore they already have access to these files. If someone has access to the rest of the files but it's allegedly "missing a flightmodel.cfg" then that's on you to figure out. It's not like someone is taking an encrypted file and hacking into it either. What's contained in the file are also not code necessarely, you're just pointing parameters to a .cfg file which are 100% things that are within the sim. Beyond that, I can't see why customer input would be irrelevant to your product. Specially when the work is already done.
    2 points
  37. The simply issue is that these files shared on .to are copyrighted files and we have no other option but to protect our copyrights otherwise you legally lose them. I explained that three times, but he simply did not want to accept the files are copyrighted. The fact they are simple 'text' files that you can read does not change that. A book also contains readable text and is also fully copyrighted. What was shared in that file was for 95% the code Hans Hartmann wrote and simply cannot be shared freely. It is what we sell. If he would have asked if he could include that we might have given permission (assuming all parties involved would agree, which I am not al all sure off). There is also absolutely no problem with the fine work he did. If he explains what to change to to the results there would absolutely not be an issue. Or if he just shares the lines that he changed that would not be an issue. It is regrettable that he now draws so much attention to his copyright violation. Just dumping our code, without license, in a freely accessible file, is illegal. It is a copyright violation. I am sure Martin did not intend that and we do not take offense. His advise has been very welcome and will always be very welcome.
    2 points
  38. A few threads on this forum has requested a way to access the essential switches like DC source, DC Master, Fuel pumps etc. via simconnect variables. Unfortunately these seem to be controlled by Bvars only accessible by mouseclicks inside the sim. Lorby's third party Axis and Ohs software (payware) has an experimental feature to map Bvars to Lvars so they can be mapped to external controllers or used in Stream Deck scripts. It's all WIP, but I've manage to map the following DC Source DC Master Condition/Fuel Levers (thanks to Lorby) Engine starter Generator left/right Fuel Pumps fwd/aft Standby Fuel Pumps fwd/aft Pitot heat Window heat Feel free to use the mappings in your own scripts. Download https://flightsim.to/file/27128/dhc-6-twin-otter-bvar-mappings-for-lorby-s-axis-and-ohs-wip
    1 point
  39. yes... may be... I am flying today to KOMA (Omaha), and may be saturday or sunday to KORD.... 🍷
    1 point
  40. I like that you have stopped in Salt Lake City and will be stopping in Omaha, Nebraska, both stops made by Phileas Fogg on the Pacific Railroad. While I won't be stopping at either, I plan to fly over them to pay homage on my way to Chicago (KORD) via Denver (KDEN). Perhaps you, me and @Mr. Jones can meet for drinks at KORD at the same time this time. I will be there tomorrow afternoon through Sunday mid-day. Best regards...
    1 point
  41. The next leg the following day was completely different than originally planned a few weeks back. Actually I intended to continuie to Phoenix AZ to meet my brother and family, who are living there for almost 30 years, and then continue to Kerrville TX to visit the birthplace of my Mooney and then continue via Dallas and Nashville in the direction of Cincinatti but that was too time consuming due to my currently "bitchy" system. So today's flight was a full 991NM to Kansas City International KMCI. The flight was quickly planned, the weather was good and it went without major obstacles past some airspaces direct-to Kansas City. Flying can be that easy. 🙂 After 5:28h flight time I reached my destination, there was only a slight tailwind but that's still better than a headwind. 60 gals AVGAS were consumed, that's 11.0 gals/h, with an average speed of 181 kts. # Der nächste Abschnitt am Tag darauf war dann völlig anders als geplant. Eigentlich wollte ich weiter nach Phoenix AZ um dort meinen Bruder und seine Familie zu treffen, der dort seit fast 30 Jahren lebt und dann weiter nach Kerrville TX um die Geburtsstätte meiner Mooney zu besuchen und dann weiter über Dallas und Nashville in Richtung Cincinnati aber das wurde mir dann doch zu zeitaufwändig aufgrund des aktuell zickigen Systems. Also ging der Flug heute in die vollen: satte 1.835km nach Kansas City International KMCI. Der Flug war schnell geplant, das Wetter war gut uns es ging ohne größere Hindernisse an einigen Lufträumen vorbei direkt nach Kansas City. So einfach kann fliegen sein. Nach 5:28h war ich am Ziel, es gab zwarn nur leichten Rückenwind aber das ist immer noch besser als Gegenwind. 60 gals AVGAS wurden verbraucht, das sind 11,0 gals/h, bei einer Durchschnittsgeschwindigkeit von 181 kts. Pre-Flight preparations in Las Vegas (default XP11 scenery). Taxiing to the active - quite a lot of business jets parked here Bye-bye Las Vegas... - I never liked the city but now I am even more disappointed with the scenery... Lake Mead from above Glen Canyon National Recreation Agriculture in Colorado ...and Kansas Closing in to Kansas City some clouds were building to the South-East but that remained isolated Fort Leavenworth at the Missouri River Turning final Taxiing to the ramp (again a detault XP11 airport) That's it for now... - I'm half-way thru the country on my way to New York. Next leg will be to Cincinnati Northern Kentucky International Airport, magnificantly done by Skyline Simulations! I'm looking forward to getting there... 🙂 Das war's für heute... - den halben Weg durchs Land nach New York habe ich hinter mir. Der nächste Flug geht nach Cincinnati Northern Kentucky International Airport, der von Skyline Simulations in eine bemerkenswerte Payware-Szenerie umgesetzt wurde und ich freue mich darauf dort anzukommen! 🙂
    1 point
  42. Yes, I’d like to hear something other than the boilerplate response in all the threads that were locked for no reason. You mention you’ll lose your copyright but you appear to be conflating copyright and trademark. Surely, distributing these mods for free falls under fair use, in any case. Also, have you offered to actually help these modders make their contributions compliant? Is that even technically possible?
    1 point
  43. 70th and final leg at the 7th stage: Columbus OH (KCMH) - New York LaGuardia (KLGA) BIG SURPRISE at the flight preparation for the final leg to NYC! After the newest Sim update the MSFS doesn't work! I forgot to back up and to deactivate the Community folder - obviously some Addons are incompatible. And today it's the last day to go to NYC if I want to follow Phileas schedule. Hmm... In the past I've spend a lot of money into the X-Plane11. Let's look if I can reactivate the good old one and if I remember how it works! I need some trials. My most expensive Payware Airplane (A320) needs updated...but not now! Therefore I decided to use the twin of the FBW A320 - the Zibo B737-800. Both are great freeware Airplanes! Ready for departure on Rwy 28L Always looking to find out to all these views like used in the past... The weather is a team player and make nice views possible to the Big Apple! We are cleared for the visual approach for Rwy 31 at LaGuardia Airport. Runway in sight - I enjoy this really great Airplane. Few seconds until the smooth landing. Easy replay funtion without extra tools - would be great in the MSFS too! This was a real nice journey into my previous Sim. I guess I will start this Sim again. Another lesson which I learned through this event! Distance: 439 Nm Flight time: 1h30 But now I need to understand why the MSFS doesn't started...
    1 point
  44. I agree here. We're paying for the product, if someone can make it better for free and you're not incorporating it to your product, it's on you. Without this mod I wouldn't have put any more than 1 hour or so on it. The stiff posture against community mods from aerosoft will make me not buy it again, after all, at some point, they might start selling liveries and saying that "Modifying our original texture files are copyright infringement" and I don't want to be sucked into this sinkhole. Aerosoft will not ever again get another penny from my wallet.
    1 point
  45. Leg 26, San Francisco – Sioux City, 4:38 hrs. 1275 miles After some wonderful and exciting days in San Francisco, the crew met at the aircraft on this foggy morning. After the usual thorough inspection of our trusty DC-6, we departed for this long flight. Crossing the Rocky Mountains eastbound. Reaching Nebraska. Parked at Sioux City, Iowa
    1 point
  46. Day fourty-six: Thursday March 3th San Francisco to New York LEG2: KSAC Sacramento - KSLC Salt Lake City cont. Early morning start at UT65 Goshute: Heading Salt Lake City: Salt Lake: APPR Salt Lake City Intl KSLC: Parking KSLC, next to a colleague ;-):
    1 point
  47. A screenshot or video showing the TO waypoint on the MFD map and on the CDU would help here. The FMS of this addon currently has several bugs, including an inconsistency of the active (TO) waypoint on the MFD and the CDU. As a result the aircraft "desperately flops back and forth" as you mentioned.
    1 point
  48. On Monday Feb 21st, I decided to go from Reno to Missoula, Montana, using an excellent aircraft simulated by Aerosoft, the Bombardier CRJ700, undera Horizon Airlines livery. Why Missoula? Well, because I have been in Missoula, around 1982 to show an Embraer E110 Bandeirante cargo and paratrooper version, to the US Forestry Service, and I wanted to see the place after so many years. By the early eighties, this aircraft type was been delivered to the Brazilian Air Force only, (that bought 10 of them, after one month of demo flights, that I made for them, on the Brazilian Amazon region). Due to the circunstances, Embraer borrowed a cargo plane from the air force, crewed by the military, to make this trip, and asked me to go along, for the local demo flights. The US Forestry Service wanted to know if the Bandeirante would serve to drop troops of their Smoke Jumpers personnel over forests on fire, to extinguish them. One of their bases were, and still is, in Missoula. I copied a short text explaining their work: “Smokejumping was developed as a means of quickly reaching, parachuting to, and initial attacking fires in remote roadless areas.The primary mission of smokejumpers is firefighting. Smokejumpers may be delivered to a fire via helicopter, vehicles, and by foot. Smokejumpers are a national resource and occasionally used as a 20-person Type 1 Crew. Region 1 maintains a force of approximately 80 smokejumpers in Missoula, Montana; 29 in Grangeville, Idaho; and 24 in West Yellowstone, Montana. Grangeville and West Yellowstone both operate as independent bases, however, training and out-of-Region fire dispatches are conducted from Missoula. Smokejumpers are dispatched to fires on Forest Service land in Montana, Idaho, and North Dakota, state-owned Forests, Bureau of Indian Affairs, and the Bureau of Land Management. Smokejumpers are often dispatched to other Regions to assist with fire suppression.” We stayed about a week in Missoula, dropping smokejumpers, heavily equipped (with shovels, tree cutters, axes, camping devices, etc), helmets with face protectors (to jump over the trees). It was amazing and gave me a great respect and admiration for their work, that has now more than 75 years of activity, during which they lost or injury many people. Finally, they did not buy the Bandeirante, which really seemed small for their task. Nowadays, they operate the Shorts 330 (picture below), which has a more spacious fuselage. During the flight from Reno to Missoula, I could not reach the SimBrief planned cruise level of 35,000 ft, so I stayed at 31,000 ft, moreover I could not capture the Missoula runway 12 ILS. The FMS changed automatically to the ILS frequency and the APPR button was pressed and lighted, but the PFD indication stayed on vertical path angle, with no flight director indication at all. Fortunately I could see the runway, and the arrival was not a problem. Pics: 1 - SimBrief route from Reno, NV to Missoula, MO 2 - CRJ700 at a Reno Int´l gate 3 - Taking off from Reno Rwy 16R 4 - Initial climb 5 - Snow fields 6 - Sunny cold 7 - Still climbing 8 - Cruising at 31,000 ft 9 - Still cruising 10 - Blue skyes 11 - Close up 12 - Beginning the descent 13 - Montana 14 - Setting landing elevation 15 - Beginning ILS Z runway 12 procedure at Missoula 16 - From outside 17 - Approaching Missoula 18 - Final 19 - Short final 20 - Landed at Missoula 21 - At Missoula Smoke Jumpers ramp 22 - Smoke Jumpers p1 23 - Smoke Jumpers p2 24 - Smoke Jumpers p3 25 - Smoke Jumpers p4 26 - Shorts 330 aircraft p5 27 - Smoke Jumpers p6
    1 point
  49. I would propose that the problem is not that you produce other products, but that you seem to rely on a single key developer for multiple products. Meaning one product like the CRJ is left in what I would describe as a fairly bug-riddled state by choice, while said single developer is off working on multiple other projects. Note that I am not saying it is unusable, but it is just not what it was claimed to be. Even 'normal ops simulation' is not quite possible and will have you encounter multiple issues. Add a lack of communication on top of that and it is just not a very good customer experience. We are closing in on the anniversary of the CRJ for MSFS, but unfortunately also on the anniversary of some of the open issues of the CRJ for MSFS. And that is very disappointing.
    1 point
  50. Hallo, ich habe mich einmal ein wenig mit der Honeycomb Hardware (Alpha Yoke und Bravo Throttle) und vor allem dem Tool Honeycomb Configurator (HC) V2.01 beschäftigt. Bitte beachten: neuere Versionen des HC können etwas unterschiedlich sein. Fragen gerne in diesem Sub-Forum mit einem neuen Topic posten (neuen Beitrag Erstellen). Den Honeycomb Configurator gibt es z.B. hier: https://forum.aerosoft.com/index.php?/files/category/126-honeycomb-profiles/ Und es gibt auch informative Video Tutorials zum Honeycomb Configurator (HC). https://www.youtube.com/watch?v=D4JJqd9B4WA&list=PL-CM2J7huv9GsJLInEaXS71CKKU_5g3Sl&index=2 Der Alpha Yoke ist ohne den Configurator leicht wie gewohnt im X-Plane 11 Menu zu konfigurieren. Die Buttons sprechen für sich. Der Bravo Throttle ist natürlich auch über das X-Plane 11 Menü - Einstellungen - Joystik zu konfigurieren: Die Schubachsen z.B. und fast alle Schalter. X-Plane 11 hat dafür bereits sehr viele Kommandos vorgesehen, die man verwenden kann. Wichtig ist der HC (Honeycomb Configurator) bei X-Plane 11 im Grunde nur für den Autopilot (linker Selektor Knopf und rechter dazugehörigen Drehknopf "increase/decrease"), die LED's (Beleuchtungen einiger Buttons und des Annunciator Panels), und vielleicht für das Trimrad (dazu komme ich später noch). Man kann natürlich auch einfach alle Knöpfe mit dem Configurator programmieren. So habe ich das gemacht um den Bravo Throttle mit dem HC besser kennen zu lernen... Der Honeycomb Bravo Throttle. Ich beschreibe hier einmal die Konfiguration für General Aviation Flugzeuge im Allgemeinen. Das funktioniert dann z.B. für GA Flugzeuge mit dem Autopiloten (AP) Bendix King (z.B. Carenado B58), dem S-TEC (Cessna 172, Thranda DHC-2 Beaver), aber auch für einfachere AP's wie z.B. verwendet in der JustFlight PA-28 Arrow III... Wobei zu bedenken ist, das dies im Grunde nur Vorschläge sind. Man kann natürlich nach eigenen Wünschen und Voraussetzungen konfigurieren... und nicht jeder AP funktioniert gleich. Da gibt es viele Möglichkeiten. Ich gehe davon aus, dass der Bravo Throttle korrekt aufgebaut und angeschlossen ist. Und ich gehe davon aus, dass der Honeycomb Configurator korrekt installiert ist. Er muss ja nur heruntergeladen und dann das Setup ausgeführt werden. Dabei dann nur das X-Plane 11 Hauptverzeichnis eintragen. Dann wird im X-Plane 11 Plugins Ordner ein plugin "AFC_Bridge" intalliert. Das ist also ganz einfach. Innerhalb X-Plane 11 kann man dann mit dem Plugin seine mit dem HC erstellten, geladenen (Profiles - Load) und aktivierten (Actions - Activate current profile) Konfigurationen einlesen: XP11 menu - plugins - honeycomb - BFC Throttle - reload bindings X-Plane 11 muss nicht gestartet sein wenn man mit dem Configurator Profile erstellt. Los gehts: Honeycomb Configurator starten. Ich habe ihn auf "englisch" gelassen, weil später die Kommandos und benötigten Datarefs in englisch bleiben. Das ist aber alles einfach zu lesen auch ohne gute Englisch Kenntnisse. Ihr könnt ihn aber über "Open Settings" auf Deutsch stellen.... Im aufgehenden Start Fenster dann den Throttle auswählen (falls man den Alpha Yoke auch besitzt). Menü Actions - Change selected device (Aktionen - Ausgewähltes Gerät ändern). Dann bekommt man ein Bild des Bravo Throttle. Man kann mit der Maus die Ansicht ändern, um alle Knöpfe zu sehen. Nun geht man auf Profiles und lädt damit das mitgelieferte Profil "Default_Throttle". Da ist schon Vieles vorkonfiguriert. Dann bitte Actions (Aktionen) - Create New Profile wählen, den Throttle nochmal auswählen und dann unter "Copy From:" das Profil Default_Throttle wählen. Oben unter "Name:" das neue Profil mit einem passenden Namen benennen (z.B. Throttle_Testprofil" ...). Dann auf "Create" klicken. Wenn ihr "Selecting profile after creating it" (Profil nach Erstellen auswählen) eingeschaltet habt, dann wird das neue Profil gleich zum weiteren Bearbeiten geladen. Ansonsten muss man es noch einmal extra laden (Menü Profile - hier das Profil anwählen - Load). So, jetzt können wir das neue geladenen Profil weiter nach unseren Vorstellungen konfigurieren ohne das Default_Profile zu ändern! Als erstes möchte ich die 7 Buttons HDG, NAV, APR, REV, ALT, VS und IAS des AP (oben) mit den passenden Funktionen belegen. Dazu als Beispiel HDG: Wir drücken in der Throttle Ansicht mit der Maus auf den Button HDG. Es erscheint ein Fenster "Select Button" mit einem blauen klickbaren Feld HDG Button. Da klicken wir drauf. Nun erscheint im rechten Teil des Fensters unter "Profile-Editor" der HDG Button. Darunter: Press-Event und Release-Event. Wir klicken auf "Press-Event" da wir ja beim Drücken des Buttons etwas bewirken wollen. Hier gibt es nun 2 Möglichkeiten: Conditions (das sind z.B. Abfragen nach einem Status.. z.B. Ist der AP an oder aus?). Variables (das sind z.B. Kommandos). Auf diesen Variables Button klicken wir, da wir ein Kommando eingeben wollen. Da kommt wahrscheinlich nichts, da ja noch kein Kommando vorliegt. Also drücken wir auf das + Zeichen um eine neue Variable (also Kommando) zu erstellen. Nun erscheint ein Feld mit 3 Eingabemöglichkeiten: EDIT variable 1: Variable: Index: Value: Wir benötigen für ein Kommando das Variable Feld. Dort muss das Kommando rein. In diesem Fall des HDG Buttons also "HDG am Autopilot einschalten". Wie das Kommando nun genau benannt sein muss, finden wir heraus indem wir die X-Plane 11 Komandos durchsuchen. Dafür gibt es ein Buttom im Konfigurator der beim Betätigen (Mausklick) zu einer Internetseite mit den X-Plane 11 Kommandos führt. Menü Actions - Open XPlane Variable List - Dataref und Commands. Wir klicken auf Commands. Auf dieser Internetseite suchen wir nach "heading" im Feld "description". Dann bekommen wir eine kleine Liste mit verfügbaren, passenden XP11 Kommandos. Wir benötigen für den HDG Knopf das Kommando "sim/autopilot/heading". Damit wird im AP die Heading Funktion eingeschaltet. Dieses Kommando muss genau so im Varable Feld des Honeycomb Confurators eingetragen werden (geht auch mit Kopieren&Einfügen). Dann klicken wir unten auf "Apply Changes". Activate profile on save sollte eingeschaltet sein. Damit haben wir den Heading Knopf konfiguriert. Wenn man das einmal verinnerlicht hat, geht das für die anderen Knöpfe nachher immer schneller.... Die Kommandos für diese 7 Knöpfe (HDG, NAV, APR usw ) schreibe ich hier mal auf. Sie sind natürlich auch auf der besagten Internet Seite zu finden. HDG = sim/autopilot/heading NAV = sim/autopilot/hdg_nav (für G1000 z.B. die Variable sim/GPS/g1000n1_nav nehmen) APR = sim/autopilot/approach REV = sim/autopilot/back_course ALT = sim/autopilot/altitude_hold VS = sim/autopilot/vertical_speed IAS = sim/autopilot/autothrottle_toggle (da bin ich mir aber noch nicht ganz sicher ...) Den ganz rechten Knopf "Autopilot" können wir z.B. mit "sim/autopilot/servos_on" definieren. oder auch ... servos_toggle. Wenn wir sim/autopilot/servos_on verwenden, dann brauchen wir noch einen Button um den AP wieder abzuschalten. Das ist dann z.B. der Wert "sim/autopilot/servos_off_any". Den kann man sich z.B. auch auf den roten Knopf am Alpha Yoke legen. ---------------------------------------- Kommen wir nun zu den beiden Drehknöpfen. Links den Selector Knopf für IAS, CRS, HDG, VS und ALT. Rechts den DECR / INCR Drehknopf. Die sollen so funktionen wenn alles korrekt konfiguriert wurde: Wenn der linke Selector auf HDG z.B steht, dann soll der rechte Drehknopf den Heading Bug nach links oder rechts bewegen. Wenn der linke Selector auf ALT steht dann soll der rechte Drehknopf die Altitude (Höhe) im Cockpit Instrument für die gewünschte Höhe ändern. usw.... Das kann X-Plane 11 zur Zeit noch nicht im eigenen Menü anbieten. Mit Hilfe des Configurators ist das aber machbar. Dazu brauchen wir nun die weiter oben kurz angeführten "Conditions" (Abfragen). Ich habe um das zu erklären einmal ein paar Bilder gemacht und füge sie hier ein. Um den linken Selector Knopf konfigurieren zu können, benötigen wir eine Selector-interne Variable. Die nennt sich: INT:FCU_SELECTOR, string Das bedeutet in diese Variable oder Condition kann man als Wert (Value) dann einen Text (string) schreiben. Den benötigen wir später für das Variablen Feld des Selectors und dann auch für das Condition Feld des INCR/DECR Knopfes. Das machen wir nun für alle 5 möglichen Stellungen des Selector Knopfs: Dann haben wir später 5 Conditions. Beispiel HDG Selection: Nach Reihenfolge der Ziffern vorgehen (Mausklick). Damit ist dann der Selector (links) für die Stellung HDG definiert. Bild 3 für Decrease. Nach Reihenfolge der Ziffern vorgehen. Bild 4 für Increase. Nach Reihenfolge der Ziffern vorgehen. Damit ist dann auch der INCR/DECR Drehknopf rechts so konfiguriert, das er wenn der Selector auf HDG steht, nun auch den Heading Bug bewegt. Wenn Activate profile on save auf ON steht, dann wird das Profil beim Speichern nun auch gleich aktiviert. ------------------------------------------- Und nun noch wie versprochen das Trimmrad. Das Trimmrad hat normalerweise die Funktion das Flugzeug zu Trimmen. Also Trim up/down oder Nose up/down. Mit ausgeschaltem Autopiloten (AP) ist das ok. Wenn aber der AP eingeschaltet ist und man das Trimmrad bewegt, dann schaltet sich der AP meist sofort aus, da man ja eingreift. Möchte man das nicht so haben, dann muss man je nach AP (On oder OFF) das Trimmrad unterschiedlich definieren. Möchte man den AP eingeschaltet lassen, obwohl man das Trimmrad bewegt (um z.B. nur ein wenig die Höhe schnell zu ändern), dann muss das Trimmrad beim bewegen den AP in den Pitch-Mode schalten. Deshalb brauchen wir für so eine Konfiguration nun auch die Condition Funktion. Wir benötigen also 2 Conditions (AP ON und AP OFF), sowie jeweils 2 Variablen für Nose up und down. Hier wieder die Bilder dazu. Hinweis: Das ist nicht bei jedem AP gleich. Da muss man etwas mit den Condition - Datarefs probieren. Autopilot OFF (Value = 0): Bild 5 Trim up Bild 6 Trim down Autopilot ON (Value = 2): Bild 7 Nose up Bild 8 Nose down Ein kleiner Tipp (von BenBaron) wenn die Auflösung des Trimrades zu gering ist (man muss dann sehr oft drehen, bevor sich etwas tut): Dann bitte den Schalter "Repeat Activation" einschalten nachdem man die Variable eingegeben hat. Ich hoffe, das hilft erstmal weiter..... Fragen gerne in diesem Sub-Forum mit einem neuen Topic posten.
    1 point
×
×
  • Create New...