|
Post by sunny9850 on Feb 1, 2011 15:40:31 GMT -5
Hi, I am still with FS9 and therefore will not be able to partake of this wonderful looking bird until later...however I will just add that I don't use the VC now for any airplane and have used Doug Dawson's View Skip gauge to get rid of them. Glenn's C-87 is what I crash in now. Andy. I tried Glenn's C-87 and while it is nicely done I still prefer a VC over the view-skip that is inevitable with 2D panels. In this particular case the only alternative is the other C-87 which was released at almost the same time and does come with a VC....but that just happens to be pretty much useless for anything but sightseeing and the last few visual moments of a flight during the downwind-base-final turns. I looked into modifying that one but the few VC gauges are hard coded in the mdl file. In case of the C-47/DC-3 we are fortunate to have an almost perfect example with a VC to fly already. So for me that one will win over a no-VC airplane every time.....even if the other option comes from Manfred Cheers Stefan
|
|
|
Post by oldpropfan on Feb 2, 2011 1:10:50 GMT -5
Hi Manfred,
I have copies of the Gmax DC-3 files that Phil Taylor had posted on his blog when Aces was together. He used them as an example of how to convert 3DSMax files for use in Gmax. Maybe you could use the interior file as the basis for a VC for your bird?
Let me know if you're interested and I'll send them to you.
Looking forward to the release of your DC-3, it looks better and better with each new picture.
Al
|
|
|
Post by mjahn on Feb 2, 2011 15:41:01 GMT -5
@warren, Yes one or two plan view pics might be useful. al, doesn't this raise copyright issues?
|
|
|
Post by aspen31 on Feb 2, 2011 15:48:39 GMT -5
Hi Manfred It may take me a couple of days to dig my way in to the propeller but I would be happy to take some photos. This prop has black blades with 4 inch yellow tips indicating an serviceable overhaul I think. There is a de-icing ring on the back of the hub but no hoses are connected. Perhaps I can send them by PM. I'm not too accomplished at including photos on a forum post. Let me know. Warren
|
|
|
Post by Tom/CalClassic on Feb 2, 2011 17:24:30 GMT -5
Manfred,
I think someone has already released an FSX DC-3 with proper lettering on each side of the tail from that GMAX file without much hoohaw, so I assume if you are careful with the credits there wouldn't be a big problem either? Since it's included in the SDK (and I don't think the SDK says you cannot use the example files in your own work) it shouldn't be a big deal?
Hope this helps,
|
|
|
Post by oldpropfan on Feb 3, 2011 3:42:29 GMT -5
Manfred,
Pretty much what Tom said I think covers it. The source files for the DC-3 were released with the FSX SDK and used by the Awesume4sum group in their mod of the DC-3. I would think that as long as proper credit is given for using the base files there should be no problem.
This is from the end of the article explaining the conversion process:
Summary The entire conversion process of the exterior and interior of the Max FSX SDK DC-3 example took a little more than 15 hours of time in total. This shows that BFF is a very practical tool for 3DSMax modelers who wish to get their creations into GMax. This exercise would be a big task for any tool and exposed many issues that one would be unlikely to encounter in practical usage. For example, you may have already imported many of the materials you plan to use and therefore won’t encounter such a large list of materials to import. We hope this article is of use to some of you who were previously unaware of the BFF script. Thanks again to John and Chuck. Hopefully many of the talented GMaxers out there can now uncover some of the FSX mysteries with the FSX SDK example in GMax, the DC-3 “Gooney Bird.”
Acknowledgements I want to thank John Walton for the main body of work in creating this article and Chuck Jodry for helping coordinate it; I just polished and edited it.—Phil Taylor ©Copyright 2008, Microsoft Corporation. All Rights Reserved
Al
|
|
|
Post by mjahn on Feb 3, 2011 4:08:55 GMT -5
Warren, no hurry, and you can send via email or get in touch via PM for exchange of addresses.
Al, can you give me a link to that article "explaining the conversion process"? I am particularly interested in the copyright aspect.
The disclaimer on the Awesome 4some edition reads thus -
I'm not too keen to take a walk on that rope.
|
|
|
Post by volkerboehme on Feb 3, 2011 5:11:21 GMT -5
Hi Manfred,
here's text from the FS2004 SDK EULA, for FSX it is probably more or less the same:
________________________________________________ 1. GRANT OF LICENSE. This EULA grants you the following rights:
Applications Software. You may install, access and run (“RUN”) the SOFTWARE PRODUCT on an unlimited number of computers, including workstations, terminals or other digital electronic devices ("COMPUTERS") to design, develop, and test software application products that are designed to operate in conjunction with Microsoft Flight Simulator 2004: A Century of Flight and subsequent versions thereof (“Application”). Sample Code. You may modify the sample source code located in the SOFTWARE PRODUCT’s “samples” directories (“Sample Code”) to design, develop, and test your Application. You may also reproduce and distribute the Sample Code in object code form along with any modifications you make to the Sample Code, provided that you comply with the Distribution Terms described below. For purposes of this section, “modifications” shall mean enhancements to the functionality of the Sample Code. ...
2. DISTRIBUTION TERMS. You may reproduce and distribute an unlimited number of copies of the Sample Code and/or Redistributable Code (collectively "REDISTRIBUTABLE COMPONENTS") as described above, provided that (a) you distribute the REDISTRIBUTABLE COMPONENTS only in conjunction with, and as a part of, your Application; (b) your Application adds significant and primary functionality to the REDISTRIBUTABLE COMPONENTS; (c) the REDISTRIBUTABLE COMPONENTS only operate in conjunction with Microsoft Flight Simulator 2004: A Century of Flight and subsequent versions thereof; (d) you distribute your Application containing the REDISTRIBUTABLE COMPONENTS pursuant to an End-User License Agreement (which may be “break-the-seal,” “click-wrap” or signed), with terms no less protective than those contained herein; (e) you do not permit further redistribution of the REDISTRIBUTABLE COMPONENTS by your end-user customers; (f) you do not use Microsoft's name, logo, or trademarks to market your Application; (g) you include a valid copyright notice on your Application; and (h) you agree to indemnify, hold harmless, and defend Microsoft from and against any claims or lawsuits, including attorneys' fees, that arise or result from the use or distribution of your Application.
[Highlights are mine] ____________________________________________________
It's legalese of course, but the way I read it, it means that you may use the sample GMAX file, modify it and use it for your own purposes. Using parts of a default VC (the wing views would probably be still yours) for a completely new DC-3 project is certainly adding significant funcionality to the original code.
I'm not quite sure why we're so sqeamish about it, anyway. Nobody even raises an eyebrow if someone modifies default DC-3 gauge code etc. or adds the original gauges into a download, often without proper identification of the original source.
You wouldn't pretending that the VC is all yours, anyway.
Just my 2 cents.
Best regards, Volker
|
|
|
Post by oldpropfan on Feb 4, 2011 1:20:47 GMT -5
Hi Manfred, Here is the link to Phil Taylor's blog post: blogs.msdn.com/b/ptaylor/archive/2008/07/28/article-on-how-to-convert-3dsmax-content-for-use-with-gmax.aspxIn the post is a link to the full conversion article and also a link to the converted DC-3 files, which is still active, and to download them you have to agree to this EULA: Microsoft Public License (Ms-PL) This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software. 1. Definitions The terms "reproduce," "reproduction," "derivative works," and "distribution" have the same meaning here as under U.S. copyright law. A "contribution" is the original software, or any additions or changes to the software. A "contributor" is any person that distributes its contribution under this license. "Licensed patents" are a contributor's patent claims that read directly on its contribution. 2. Grant of Rights (A) Copyright Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free copyright license to reproduce its contribution, prepare derivative works of its contribution, and distribute its contribution or any derivative works that you create.(B) Patent Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free license under its licensed patents to make, have made, use, sell, offer for sale, import, and/or otherwise dispose of its contribution in the software or derivative works of the contribution in the software. 3. Conditions and Limitations (A) No Trademark License- This license does not grant you rights to use any contributors' name, logo, or trademarks. (B) If you bring a patent claim against any contributor over patents that you claim are infringed by the software, your patent license from such contributor to the software ends automatically. (C) If you distribute any portion of the software, you must retain all copyright, patent, trademark, and attribution notices that are present in the software. (D) If you distribute any portion of the software in source code form, you may do so only under this license by including a complete copy of this license with your distribution. If you distribute any portion of the software in compiled or object code form, you may only do so under a license that complies with this license. (E) The software is licensed "as-is." You bear the risk of using it. The contributors give no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, the contributors exclude the implied warranties of merchantability, fitness for a particular purpose and non-infringement. Looks to me like section A pretty much covers any questions as to use and distribution. Al
|
|
|
Post by mjahn on Feb 4, 2011 3:36:16 GMT -5
Thanks Volker and Al (for the free legal advice), will look into this.
|
|
|
Post by Johan Dees on Feb 4, 2011 17:14:27 GMT -5
Manfred, its a non issue, please continue.
|
|
|
Post by mjahn on Feb 12, 2011 15:19:05 GMT -5
Not this weekend but ... I am working on the paintkit now. There is going to be two versions, one wartime, with a typical set of aerials, and one post-war, with one/two beacons. This is Bernhard's rendering of "Turf Sport".
|
|
|
Post by Johan Dees on Feb 12, 2011 15:26:32 GMT -5
Is Bernard here too ? mein himmel!
looks good, any VC shots?
|
|
|
Post by Connie Flyer on Feb 12, 2011 16:34:54 GMT -5
Looks great Manfred!
|
|
bytes
ConvairLiner
Posts: 98
|
Post by bytes on Feb 12, 2011 18:09:06 GMT -5
This could easily pass as a real picture. You and those of your team have my greatest praise for your work. Just shoved another DC-3 out the hanger door to make room Russ
|
|