TheSpecial

Sorry guys, but I suggest you to stop the discussion about freeware/payware. I fully understand the decision of Pete. Actually it is a good decision. Payware developers are making money by using something he developed, he deserves to get money for this! Greetz

That's a great relief, that's somehow simular to my second suggestion. It would be very nice if freeware products would be able to interface FSUIPC! I know that programming costs much time, that's true, certainly FSUIPC since there are a lot of people that are on your back (especially when a new FS version gets released), therefore I would also like to thank you. You've already done a great job! I actually was worring... But my worries are over now, centainly if you try to keep the interface for freeware programs. :) Greetz & Good Luck!

Hi Pete, I would like to know if you decided yet about the fact to make FSUIPC shareware or not? First of all let me say that I really appreciate your work for FSUIPC, you've done a great job for the whole FS community. Now, let me come the my main point of this topic (please don't delete it). Currently I'm doing my studies for Informatics at the Free University of Brussels, so I know very well what programming is and how much time it can take. But, in those years I've learned also that you can get such a great feeling by releasing products for free instead of charging people for it. Most people call this the spirit of free software or even open source! Let me make my point a bit clearer, many Flight Simulator products depend on FSUIPC this goes for freeware and payware products. When you make people pay for the FSUIPC this will force all the freeware software that uses FSUIPC to look for another FSUIPC or let the products go payware (which most products won't do I think). Off course I can understand you can use the money, but may be there are other solutions. Here are some: First one: you create a sort of license which allows freeware products to use and package FSUIPC for free, and payware products to use and package FSUIPC for a specified amout of money, may be even a percentage of their sales price. Second one: create 2 FSUIPC products, one that has the features FSUIPC now has and that supports the coming FS products also, and a second version with more advanced features. The second version would be payware then. Third one, this is probably the most controversial one. Release the source code of the current FSUIPC version (which doesn't support FS2004) and let the open source developers take over that part of the project, you can develop your part of the project yourselves, but you have the advantage that you have experience with Flight Simulator. I hope you respect my opinion and may be take it into your memory. Thanks for reading my topic. At last I hope that you do so of my suggestions it would be better for all of us! Greetz

Oki, thx for the information! 8)

Oki, thx for the information! 8)

Hi, For HomeFLY, my project that uses FSUIPC, I would like to know if it is possible to catch the aircraft type (Boeing 737-300, Airbus A320-200,...) for all FS versions (FS98,2000,2002)... I've found an offset, but it seems only to work with FS2002. If this isn't possible, would it be possible to catch the aircraft's name (also in all FS versions). Thanks!

Hi, For HomeFLY, my project that uses FSUIPC, I would like to know if it is possible to catch the aircraft type (Boeing 737-300, Airbus A320-200,...) for all FS versions (FS98,2000,2002)... I've found an offset, but it seems only to work with FS2002. If this isn't possible, would it be possible to catch the aircraft's name (also in all FS versions). Thanks!

Thx for the info, I'll try to figure it out :)

Hi, I'm using the SDK Release13, can anyone point me at the most importent changes since that version? Or is this note in some document? Thanks!