Re: [Flightgear-devel] SimGear build fails
Am 2013-06-26 22:43, schrieb Alex Romosan: > these are the changes i made to get simgear to compile with > openscenegraph from svn: Thank you Alex! I've just commited your patch. Tom -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] SimGear build fails
Torsten Dreyer writes: > I'm failing to build SimGear on 64bit linux: > EffectGeode.cxx:83:136: error: no matching function for call to > ‘osg::Geometry::setVertexAttribArray(int&, osg::Geometry::ArrayData)’ > > OSG is stable 3.0.1 from svn (same with OSG trunk) > SimGear is git next from today > > Yes, I rm-rf'ed previous artefacts and started from scratch. these are the changes i made to get simgear to compile with openscenegraph from svn: diff --git a/simgear/scene/material/EffectGeode.cxx b/simgear/scene/material/EffectGeode.cxx index 26eab38..d634ac8 100644 --- a/simgear/scene/material/EffectGeode.cxx +++ b/simgear/scene/material/EffectGeode.cxx @@ -80,15 +80,15 @@ void EffectGeode::runGenerators(osg::Geometry *geometry) int n = _effect->getGenerator(Effect::TANGENT); tsg->generate(geometry, 0); // 0 is normal_unit, but I have no idea what that is! if (n != -1 && !geometry->getVertexAttribArray(n)) -geometry->setVertexAttribData(n, osg::Geometry::ArrayData(tsg->getTangentArray(), osg::Geometry::BIND_PER_VERTEX,GL_FALSE)); +geometry->setVertexAttribArray(n, tsg->getTangentArray()); n = _effect->getGenerator(Effect::BINORMAL); if (n != -1 && !geometry->getVertexAttribArray(n)) -geometry->setVertexAttribData(n, osg::Geometry::ArrayData(tsg->getBinormalArray(), osg::Geometry::BIND_PER_VERTEX,GL_FALSE)); +geometry->setVertexAttribArray(n, tsg->getBinormalArray()); n = _effect->getGenerator(Effect::NORMAL); if (n != -1 && !geometry->getVertexAttribArray(n)) -geometry->setVertexAttribData(n, osg::Geometry::ArrayData(tsg->getNormalArray(), osg::Geometry::BIND_PER_VERTEX,GL_FALSE)); +geometry->setVertexAttribArray(n, tsg->getNormalArray()); } } --alex-- -- | I believe the moment is at hand when, by a paranoiac and active | | advance of the mind, it will be possible (simultaneously with | | automatism and other passive states) to systematize confusion | | and thus to help to discredit completely the world of reality. | -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] some models updates available
Hi Ahmad, On Sat, Jun 22, 2013 at 3:06 PM, grtuxhangar team wrote: > Hello, > > One of our member within our grthteam has been working on updates gpl > compliant regarding some old models which were done by Gérard many years > ago. > You may find these models updated at > https://gitorious.org/eekpo > you may get them with > git clone g...@gitorious.org:eekpo/f-8e-crusader.git > git clone g...@gitorious.org:eekpo/pby-catalina.git I was planning to merge these into fgdata this evening, but they appear to have been deleted last night. Are you planning to re-release them? If so, please let me know so I can get them into fgdata. It would be great to have both these aircraft updated for the 2.10.0 release. Thanks, -Stuart -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] reminder: entering feature freeze now
On 25 Jun 2013, at 22:48, Stuart Buchanan wrote: > Declaring that the Feb 2014 release will be 3.0 now will give everyone plenty > of > notice, and might encourage efforts to fix bugs in the next 6 months. I'm > aware > that my FG development time is more limited these days, and given activity on > this list I suspect I'm not alone, so this time might be quite useful. I think I sensible step in that case is to keep 3.0 as backward compatible (in terms of Aircraft APIs) with 2.12 as possible, which mostly means my resisting the urge to clean up legacy stuff :) Obviously it's tricky to offer a 100% guarantee, but I don't have anything planned for 3.0 that will require aircraft changes - I'm sure new technologies such as state machines, knob/slider animations and tooltips will mature and gain some new features but hopefully aircraft developers will be able to work against 2.12 with confidence that things will work the same in 3.0 It's a bit tricky because I haven't had much feedback from aircraft developers about the new APIs (since they aren't in 2.10), but once 2.12 ships we would want to keep them compatible, so fingers crossed the current design is sensible :) Regards, James -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Grain texture for models - a demo
> That would be appreciated. Emilian already reminded me of the normalmap > feature, so it'd be interesting to compare the two and see which one I > prefer. I don't know if Emilian gave you the notion that these would be competing options or not, but the notion isn't correct. You're not technically restricted to having either a normalmap or a grain texture, the shader allows you to have both, and they also do very different things, so it makes even sense to have both. Think of color variations in smoothly polished wood - these have no distortion of the normal, so you wouldn't do them with a normalmap, but a grain overlay works just fine. You might want to use a grain texture for details which are too small to be explicitly simulated by a normalmap as just color variations (because that's computationally and momory-wise much cheaper to do), but basically if you have surface structure on the size scale of your standard texture, you'd not normally use a grain texture to model them. Cheers, * Thorsten -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] reminder: entering feature freeze now
>> Having thought about this a bit more I'm going to propose we do 2.12.0 >> now and >> "pre-announce" 3.0 as the Feb 2014 release to give us just a little >> more time >> to prepare and make the 3.0 as polished as possible. After all, it'll >> be the third >> major release in 15 years :) . Okay, works for me as well. * Thorsten -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] reminder: entering feature freeze now
On 26 Jun 2013, at 08:42, Vivian Meazza wrote: > Makes sense to me, Yep, works for me too. James -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] reminder: entering feature freeze now
> From: Anders Gidenstam [mailto:anders-...@gidenstam.org] > Sent: 26 June 2013 07:41 > To: FlightGear developers discussions > Subject: Re: [Flightgear-devel] reminder: entering feature freeze now > > On Tue, 25 Jun 2013, Stuart Buchanan wrote: > > > Having thought about this a bit more I'm going to propose we do 2.12.0 > > now and "pre-announce" 3.0 as the Feb 2014 release to give us just a > > little more time to prepare and make the 3.0 as polished as possible. > > After all, it'll be the third major release in 15 years :) . > > Sounds like a plan. I prefer this option. > Makes sense to me, Vivian -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
