MSPhysics 1.0.3 (16 October 2017)
-
Hi faust,
Assigning unique IDs is one way to manage copied joints. Another way, a more preferable one, is by selecting the whole birdy, with its components, and clicking (Context Menu)->MSPhysics->State->Connect Closest Joints. After that, you can copy the birdy multiple times without having to assign unique IDs.
It is possible to create waves and splash effects with MSPhysics, however, just like in SketchyPhysics, there won't be much physics involved; most of it would be controlled through scripting. That said, the touch events won't respond to the bodies contacting the "artificial" waves. This will require writing additional code for determining contacts and then emitting dust or splash effects at such points. All in all what your asking for might require quite a lot of coding and I'll have to pass on that one. You can however try utilizing it yourself maybe with workarounds and simpler approaches.
Anton
-
The Connect Closet Joints - method sounds great. Will try it. Thanks!
I hope that your last sentences were based only on the coding of specials like waves and not generally on to the development of MSPhysics ...? -
Announcing 0.9.0!
-
Compatibility with Mac OS X 10.5+; still limited when it comes to managing keyboard, mouse, and MIDI, but the most important stuff is working just fine.
-
Fixed a bug where MSPhysics failed to load previous editor settings. Thanks to PituPhysics for report.
-
Joystick should work even if connected after SketchUp starts.
-
Added alignment power option to CurvySlider and CurvyPiston joints.
-
Added LinearGear, AngularGear, and RackAndPinion constraints.
-
Reworked the scripting API. Various functions were renamed and rearranged.
-
Renamed various (
get_some_method
/set_some_method
) functions, that acquired one parameter, tosome_method
/some_method=
. -
Added
BodyContext
class. All body events, such asonUpdate
, were moved to theBodyContext
. -
To reference a
Body
associated with theBodyContext
, callBodyContext.#this
. -
To reference a
BodyContext
associated with theBody
, callBody.#context
. -
Renamed
Common
andController
toCommonContext
andControllerContext
. -
Scripting scope was changed to
BodyContext
. To call body methods from the scripting scope, it is now essential to place the keyword "this" in front. -
To call
BodyContext
methods, which are mostly events, from the scripting scope, you don't need to place any keywords in front. -
Renamed
get_body_by_group
,get_group_by_name
, etc.. to [ruby:15odxhy4]find_body_by_group[/ruby:15odxhy4], [ruby:15odxhy4]find_by_by_name[/ruby:15odxhy4], etc... -
Renamed all [ruby:15odxhy4]is_some_method?[/ruby:15odxhy4] functions to [ruby:15odxhy4]some_method?[/ruby:15odxhy4].
-
Many methods that focused on general stuff were moved to AMS Library. For instance, the whole [ruby:15odxhy4]Group[/ruby:15odxhy4] and [ruby:15odxhy4]Geometry[/ruby:15odxhy4] classes were transferred to AMS Library.
-
The scripting changes were made for coding convenience and are very likely to remain unchanged in the upcoming releases.
-
Enchanted control panel and the dialog.
-
Various other bug fixes and improvements.
-
-
How process (if possible) for have and keep the tracks marks of the car moving on the terrain ?
(of each wheel) -
In my case (update from MSPhysics v0.8.0 to v.0.9.0) using the Extension Store leads to immediate failure after start of MSP (also with the new models). It seems that old files in the MSPhysics folder of v.0.8.0 partially are not deleted or overwritten. To delete the directory and copy it complete new in the plugin folder works.
-
After revising the scripts for v0.9.0 my test models work better than before. To record simulation to Replay is much faster too. Thanks!
-
The option to save the replay data in the model file has been lost ...?
-
Pilou, it's possible to create tracks, but only through scripting.
Faust, my bad. I disabled the saving of Replay animation into model because it affected performance; that's why you noticed huge performance boost in this version. I was trying to rework it, but then completely forgot about it. The fix is underway.
-
Hi Anton, do you see an opportunity to revise your MIDI-Piano for version 0.9.0?
-
Hi
To help you, to add control panel , please , take a look on the next pictures
click on the second picture to animIf you 'd like , you can test by yourself with my SKETCHUP file and change parameter.
Chri
-
Anton, I'm having problems with the UI. Here is a screen shot. It will not size into my window nor can I resize it nor does it have tabs.
Win 7, SU 2015, 64 bit.
Any help would be very appreciated.
-
Bryan, I'm not sure what's going on there. Does this show up every time you open it? Have you tried refreshing it (F5)? If the problem still persists, open explorer, and paste this into the address bar: %appdata%\SketchUp\SketchUp 2015\SketchUp\Plugins\MSPhysics\css. Then verify that the folder contains chosen.css, dialog.css, and tabs.css.
-
@anton_s said:
Bryan, I'm not sure what's going on there. Does this show up every time you open it? Have you tried refreshing it (F5)? If the problem still persists, open explorer, and paste this into the address bar: %appdata%\SketchUp\SketchUp 2015\SketchUp\Plugins\MSPhysics\css. Then verify that the folder contains chosen.css, dialog.css, and tabs.css.
Thanks.
The files are there and F5 did not change the layout. Tabs are still not showing.
-
What version of Internet Explorer do you have installed?
-
-
Anton, are you using ENV variables to obtain the path?
-
Thanks Anton. It's odd because the program installed without any trouble.
Is there a specific order the AMS library and MS Physics should be installed? I ask because I installed MS first, then AMS second.
-
Bryan, the order doesn't matter. I tested it on Win7 with IE11 and it works very well. I could reproduce what you have only by renaming/removing the CSS folder. So I don't know. It looks like the dialog.html can't determine the CSS paths or the CSS folder or the files within it are missing.
-
Brian, I'll test it out on my Windows 7 with IE11. So far it works fine on my Win7 and IE9.
Thomthom, as far as I recall I don't use ENV variables to obtain the paths. I rather modify one of them, particularly ENV['PATH'], so that
msp_lib.so
knows where to look for the required Dlls and this is only necessary on the Windows side. And instead of overwriting the ENV['PATH'] variable with the new path(s), I simply append another path to it. I don't think that should hurt other plugins or anything. Of course, I acknowledge that it would be a good idea to reset it to original paths after all the loading is done.
Edit: On the OS X Side I use install name tool to set the relative load path to the required dylibs. This can be done with xCode by adding a post build script. -
@faust07 said:
Hi Anton, do you see an opportunity to revise your MIDI-Piano for version 0.9.0?
Hi faust. I updated the MIDI piano a few days ago. It should work fine now
Advertisement