Many thanks, Mike and Radu. I appreciate the info, Mike, and your pushing the fix, Radu.
On Wednesday, May 14, 2025 at 10:09:15 AM UTC-4 Radu Serban wrote: > Hi Eric, > > > > Indeed, this was a bug I introduced a while ago while doing some > refactoring of Chrono::Vehicle. > > I pushed a fix (commit 542b16c > <https://github.com/projectchrono/chrono/commit/542b16c23d3a650f028bfa30a7f36e3b36aeece5> > > in the main branch of the git repository). > > > > --Radu > > > > *From:* [email protected] <[email protected]> *On > Behalf Of *Mike Taylor > *Sent:* Wednesday, May 14, 2025 3:21 AM > *To:* ProjectChrono <[email protected]> > *Subject:* [chrono] Re: Continuous Band Track > > > > Eric, > > > > I'm guessing my previous reply was lost with the multiple messages. > > > > "demo_VEH_M113_Band" is mainly a proof-of-concept model for a track system > composed of a mix of rigid tread blocks connected by flexible, nonlinear > finite element based, webs. As far as I'm aware, it has not been touched > for many years. > > > > It appears that this demo stopped working correctly at some point in the > recent past in the main development branch. I'm seeing similar issues when > I tested it recently with Visual Studio on Windows. It will be some time > before I'll have a chance to dive into this. In the meantime, you could > try pulling the Chrono 9.0 release and trying the demo in that version of > the code. The result should look something like the following image. > > Best Regards, > > > > Mike > > > > On Thursday, May 8, 2025 at 3:18:46 PM UTC-5 [email protected] wrote: > > Oops... I meant "demo_VEH_M113_Band.exe". It does not display any > visuals. I'm curious about possible causes (Irrlicht works fine) as well > as the state of the continuous band track development. Thanks! > > On Tuesday, April 22, 2025 at 4:25:21 PM UTC-4 Eric Patterson wrote: > > I wanted to ask those familiar with the continuous band track development > how far along is it, generally? > > > > Also, when I go to run "demo_MBS_tracks.exe", displays a printout of the > belt wrap algorithm converging, but nothing is displayed despite other > demos working. It seems like it's somewhere in the track assembly as I've > been starting to dig to debug it, but I thought someone might have some > ideas for what to check for sure in terms of packages, etc., if it doesn't > run right out of the box. > > > > Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "ProjectChrono" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/projectchrono/5c0d0e56-165f-4ccd-87ff-928a4d7203a2n%40googlegroups.com > > <https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/5c0d0e56-165f-4ccd-87ff-928a4d7203a2n*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!Ih7kVEm7O3kXoRlfh0Jow_YzGEyBDq7GF4vylpfjhYrFbckKmCn_lxXwCMDy-jA1mzY_qJIRcSPBlDthG10yNGc$> > . > -- You received this message because you are subscribed to the Google Groups "ProjectChrono" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/projectchrono/0e56c5d1-9531-480f-aef8-edf32cf08aa9n%40googlegroups.com.
