Thanks for the new adapter! Could you provide the diameter at the IUS and Centaur ends (so I can add them to the manual to give payload developers the data to do other adapters)?
Thanks for the new adapter! Could you provide the diameter at the IUS and Centaur ends (so I can add them to the manual to give payload developers the data to do other adapters)?
I'll get them tomorrow. Speaking of manuals, I think we should convert them to PDF. Currently they're in DOC format.
Urwumpe, when you have time could you look at the panel and panel group classes? I added a few new switches and found some kind of memory leak indication when closing the simulation. It was in the "scalar deleting destructor" of the panel, called from the panel group.
I eventually started to remove panels and it returned to normal. I then enabled all the panels again, and now the very same code that crashed works fine. :idk:
No deal, can do it. Maybe just a bad state somewhere.
Did you keep the error messages about that problem?
Nop... :facepalm: :facepalm:
No deal. Then I will just need to find out if there is a weakness somewhere. Maybe a good reason to do some review there and clean the code up.
A review is more of what I had in mind. Didn't you have some kind of tool to analyse the code?
Yeah, I remember something. Should I remember wrong, I just lint everything. :lol:
---------- Post added at 09:56 PM ---------- Previous post was at 04:35 PM ----------
25 issues with the code analysis of Visual Studio. Nothing related to the VC there. Most complain about how we use sscan_s, nothing serious.
There is an uninitialized memory issue in ssme.cpp which is pretty dire (bundle_power), also the bridgerail implementation in mission has a problem about array usage (A size of 13 means 12 is the highest legal index, not 12, a common C++ error).
I am a bit disappointed, because I know of more code smells, which we currently tolerate. Will look for a real tool.
I had some troubles building the Centaur and IUS projects. I solved them by adding PIDControl.cpp to the projects and ../../../libUltra/include to Additional Include directories in the Project Properties. Should I check in these changes to the projects?Added engine gimballing to the upper stages, but it needs someone with vs2013 to add libUltra or it will only compile in vs2010.
Any news on the OrbitersimBeta branch? It was created by SiameseCat but there's no activity there.....
I had some troubles building the Centaur and IUS projects. I solved them by adding PIDControl.cpp to the projects and ../../../libUltra/include to Additional Include directories in the Project Properties. Should I check in these changes to the projects?
Yes, I'm using the VS2010 solution. Yet it wouldn't build. And I just reverted the changes back to baseline rev. 2352 and have the same problems.Are you using the vs2010 projects? If so, then no changes should be needed as I updated those.
Again this is just for vs2010, for 2013 someone else has to do it.
No problem, I am still 2013 user. Should I upgrade to 2015, the confusion might become perfect. :lol:
Maybe we should try getting a Visual Studio version neutral build script one day.