<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/openrocket/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/openrocket/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 06 May 2013 19:44:29 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/openrocket/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>3D view accuracy</title><link>https://sourceforge.net/p/openrocket/feature-requests/19/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Very nice "3D Finished", but perhaps vary appearance depending on what material the component is made of (i.e. don't show a fibreglass fin as wood).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 06 May 2013 19:44:29 -0000</pubDate><guid>https://sourceforge.netca870efe5fb71dbf3d695e8fdf85eb614779f213</guid></item><item><title>More motor options</title><link>https://sourceforge.net/p/openrocket/feature-requests/18/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I would like the option to create more detailed motor shapes. Specifically it would be cool to be able to design a motor that is non-cylindrical, like one with a taper or spherical casing. Maybe even make it like the freeform fin design system. Also would need to be able to import a user created thrust curve to the newly created casing. I know that ThrustCurve tracer requires you to define motor specs, so would need to override those. &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 13 Mar 2013 18:37:32 -0000</pubDate><guid>https://sourceforge.net48869d378f8ef0e9021346bcee7c0df23b436274</guid></item><item><title>Print</title><link>https://sourceforge.net/p/openrocket/feature-requests/17/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Ability to print out designs that show basic CP-CG relationship&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sat, 31 Jul 2010 02:44:54 -0000</pubDate><guid>https://sourceforge.netafa7af09f137a02408e478401562c74672b67625</guid></item><item><title>One touch re-scaling</title><link>https://sourceforge.net/p/openrocket/feature-requests/16/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be handy to draw a model in a particular scale e.g 1/15. Then, prior to printing, choose a new scale for the final model e.g. 1/24. This means you could have one drawing and then produce a blue print for any size model you want. This is useful when you are copying a design for a model thats not the size you want to fly or display.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 26 Jul 2010 13:23:35 -0000</pubDate><guid>https://sourceforge.net4174c4fe5400c92a3df70cb95ad09db7d30bfd7a</guid></item><item><title>Automated optimization</title><link>https://sourceforge.net/p/openrocket/feature-requests/15/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Have the ability to optimize components of the rocket to achieve desired effects in the flight (max/specific altitude, max/specific velocity, etc.).&lt;br /&gt;
A limit to the scope of the allowable changes would probably be desired (if not imperative) to keep within a reasonable computation period, perhaps some sort of maximum relative change from the current rocket state.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">evan</dc:creator><pubDate>Wed, 21 Jul 2010 17:30:59 -0000</pubDate><guid>https://sourceforge.neta2589725ba5291cbcc8e9131dfaeb7f5a506e7e3</guid></item><item><title>printing out FULL SIZE fin templates</title><link>https://sourceforge.net/p/openrocket/feature-requests/14/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;if we could do this we just go over the balsa and use the template as a tracer it would help alot&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Tue, 16 Feb 2010 03:11:46 -0000</pubDate><guid>https://sourceforge.net5170a7c9e50b8974f80337b81ad097c008bc4bf2</guid></item><item><title>Use standard component naming</title><link>https://sourceforge.net/p/openrocket/feature-requests/13/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be much nicer to build rockets in OR if I could, in addition to being able to specify body tubes and nose cones by exact dimension, if I could select, for example BT-20 tubing and have OR already know the ID and OD.&lt;/p&gt;
&lt;p&gt;(If this is what is meant by the future development item "Support for ready-made component databases" ,then ignore this feature request.)&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 18 Jan 2010 21:51:17 -0000</pubDate><guid>https://sourceforge.net08aa155e63d0bff068177edfdc3fd455bfc0d151</guid></item><item><title>print templates</title><link>https://sourceforge.net/p/openrocket/feature-requests/12/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be helpful if OR could print out (to scale)&lt;br /&gt;
fin templates (including thru-wall-tabs)&lt;br /&gt;
transition section templates&lt;/p&gt;
&lt;p&gt;not really a fancy item, but a helpful tool present in VCP, spacecad and Rocksim&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 18 Jan 2010 21:47:52 -0000</pubDate><guid>https://sourceforge.net0ce15abb630b936d16f6aea70e4d8fe17432d004</guid></item><item><title>analysis seems overly sensitive to fin position</title><link>https://sourceforge.net/p/openrocket/feature-requests/11/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I have noticed that the peak altitude attained by a rocket with four fins 90/90/90/90 degrees apart, is predicted to be significantly higher than the same rocket with fins 90/90/92/88 degrees apart.  (both analyses run without any wind).&lt;br /&gt;
I don't have any data to back this up, but it seems suprising that 2 degrees of mis-position would cause a 8-10% loss in altiude.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 18 Jan 2010 21:44:28 -0000</pubDate><guid>https://sourceforge.netb23b6336931974d6a5e8b6bb152be3545e7f3c8a</guid></item><item><title>Thrust non-axissymmetry</title><link>https://sourceforge.net/p/openrocket/feature-requests/10/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I've noticed that if I build a cluster rocket, but use different motors in the different positions, (for example a triangular cluster with 2xB6-4 and 1xC6-5, the rocket still flies straight "up" (when there is no wind).  It looks like the thrust is being calculated as the sum of the three engines, but all acting at the centerline of the rocket (axissmyetrically).  In the real world, there the thrust vector would be off-axis so there would be an imparted picthing moment.&lt;/p&gt;
&lt;p&gt;The real reason to simluate this behavior is for the case where the engines are symmetrical and equal thrust, but they ignite at slightly different times - or in the even of a large cluster rocket where one or more engines fails to light at all.&lt;br /&gt;
&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 18 Jan 2010 21:40:37 -0000</pubDate><guid>https://sourceforge.netf79c75d9cc826b564712af0eb21f38392b63794d</guid></item></channel></rss>