MSPhysics 1.0.3 (16 October 2017)

jeep906

Dear author! I apologize for my English, I translate Google translator.
Is it possible to save the properties of individual objects defined in the MSPhysics UI tool when combining these objects into a common group?
if there is no such possibility in this plugin, I am ready to pay for writing a new one, where there is such an opportunity. Please help me!

tayyab2224

As far as i know , it is not possible in this version, anton_s might be busy anywhere else .

Anton_S

@jeep906 said:

Dear author! I apologize for my English, I translate Google translator.
Is it possible to save the properties of individual objects defined in the MSPhysics UI tool when combining these objects into a common group?
if there is no such possibility in this plugin, I am ready to pay for writing a new one, where there is such an opportunity. Please help me!

With the current version, it is not possible to assign properties to internal groups. The new version, that I am developing, will support this functionality.

@tayyab2224 said:

As far as i know , it is not possible in this version, anton_s might be busy anywhere else .

I am honestly working on the project, just not as actively. I have been focused on other things. NewtonDynamics, the physics engine used by MSPhysics, has become much more stable and robust with joints than before. We will no longer experience the weird behavior of those flexible and wandering joints and have much better experience with developing robotics. I am driven to develop the new version. Thanks for your interest in the project!

faust07

Thanks for the information on the further development of MSPhysics. That sounds great. Will the old models be compatible with the new version?

Anton_S

@faust07 said:

Thanks for the information on the further development of MSPhysics. That sounds great. Will the old models be compatible with the new version?

Unfortunately MSPhysics 2 won't be compatible with current models. This time, any object intended for simulation will have to be marked explicitly, rather than excluding unwanted with the Ignore option. Scripting docs is going to be different as well. My intention is to focus on usability and tutorials with this one.

Hza

Hello Anton, thanks for the great extension! Please, when we can expect release of the MSPhysics 2?
thanks again!
Hza

@anton_s said:

@faust07 said:

Thanks for the information on the further development of MSPhysics. That sounds great. Will the old models be compatible with the new version?

Unfortunately MSPhysics 2 won't be compatible with current models. This time, any object intended for simulation will have to be marked explicitly, rather than excluding unwanted with the Ignore option. Scripting docs is going to be different as well. My intention is to focus on usability and tutorials with this one.

Anton_S

@hza said:

Hello Anton, thanks for the great extension! Please, when we can expect release of the MSPhysics 2?
thanks again!
Hza

The first beta version should be ready in a few months.

jumpjack

Does it exist a library of mechanisms for MSP? I can find only a dozen models on warehouse.

kaoru_komine

I am commenting for the first time.
Thanks to the author for the great plugin.
I'm looking forward to the new version of "MSPhysics".

Now, I have a question about "MSPhysics2".
I use Ruby scripts that can be input from the UI to control the 3D model in the current "MSPhysics".Is it possible to do the same thing with "MSPhysics2"?

Anton_S

@kaoru_komine said:

I use Ruby scripts that can be input from the UI to control the 3D model in the current "MSPhysics".Is it possible to do the same thing with "MSPhysics2"?

Yes, scripting will still be available with MSPhysics2. The scripting API will be different, however.

Anton_S

@jumpjack said:

Does it exist a library of mechanisms for MSP? I can find only a dozen models on warehouse.

As mentioned earlier, MSPhysics 1 has weak joints, in which case creating mechanical interconnections between rods, suspension, robotic arms, and what not, makes the resulting structure weak and loose, unless all interconnected groups have an identical mass. MSPhysics 2 should be able to address this issue. I haven't yet tested that, and I am a little behind with my promises on the development of the project, but as mentioned earlier, I am very exited to utilize the newer NewtonDynamics version for this, which showed promising results with the stable and robust interlinked joint behavior.

tayyab2224

@anton_s said:

@jumpjack said:

Does it exist a library of mechanisms for MSP? I can find only a dozen models on warehouse.

As mentioned earlier, MSPhysics 1 has weak joints, in which case creating mechanical interconnections between rods, suspension, robotic arms, and what not, makes the resulting structure weak and loose, unless all interconnected groups have an identical mass. MSPhysics 2 should be able to address this issue. I haven't yet tested that, and I am a little behind with my promises on the development of the project, but as mentioned earlier, I am very exited to utilize the newer NewtonDynamics version for this, which showed promising results with the stable and robust interlinked joint behavior.

I hope we will enjoy MSP2 this summer۔۔۔

daniabreu1

Looking forward to see the new version of this plugin that it will work on new versions of SU. Keep updating us! Thank you!

tayyab2224

What if flying simulation in msp2 ?

Anton_S

@tayyab2224 said:

What if flying simulation in msp2 ?
You mean aerodynamics? I am planning to implement Newtonian drag (already developed in ClothWorks for simulating flags and parachute effects). Newtonian drag alone does not provide accurate results, as it does not involve turbulence and additional actors, but should yield useful results for simulating wings.

sheadacus

Hello is there anyway to combine a slider and servo motor. Similar to the corkscrew but I need it to move apart automatically in twisting and sliding a certain distance and angle. Whenever I do a slider I cant move the servo and vice versa.

Anton_S

@sheadacus said:

Hello is there anyway to combine a slider and servo motor. Similar to the corkscrew but I need it to move apart automatically in twisting and sliding a certain distance and angle. Whenever I do a slider I cant move the servo and vice versa.

Hi! Yes, there is. To do this, you need two groups. One way to do this is by having slider as a top level joint and servo as an inner level joint:

Create two box groups positioned next to each other.
Create a slider joint at the top level, next to group A.
Create a servo joint, one level inside group A.
Using the joint connection tool, connect servo to group B.
Then, connect slider to group A.
In this scenario, group A will be constrained to the slider and group B will be constrained to a servo, with respect to group A.

mauroa6

Good morning
I installed MSPhysic 1.0.3 and related AMS 3.6.0h libraries, but when opening SketchUp I get this error ...
Thanks

Errore di caricamento del file C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/MSPhysics/main_entry.rb
Error: #<IOError: The required, staged c extension file, "C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/MSPhysics/libraries/stage/win64/2.5/msp_lib.so", is missing!>
C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/ams_Lib/extension_manager.rb:204:in block in require_all' C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/ams_Lib/extension_manager.rb:201:in each'
C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/ams_Lib/extension_manager.rb:201:in require_all' C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/MSPhysics/main.rb:70:in <top (required)>'
C:/SketchUp 2019/Tools/RubyStdLib/rubygems/core_ext/kernel_require.rb:59:in require' C:/SketchUp 2019/Tools/RubyStdLib/rubygems/core_ext/kernel_require.rb:59:in require'
C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/MSPhysics/main_entry.rb:15:in <top (required)>' C:/SketchUp 2019/Tools/extensions.rb:197:in require'
C:/SketchUp 2019/Tools/extensions.rb:197:in load' C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/MSPhysics.rb:21:in register_extension'
C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/MSPhysics.rb:21:in <module:MSPhysics>' C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/MSPhysics.rb:5:in <top (required)>'

tayyab2224

@mauroa6 said:

Good morning
I installed MSPhysic 1.0.3 and related AMS 3.6.0h libraries, but when opening SketchUp I get this error ...
Thanks

Errore di caricamento del file C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/MSPhysics/main_entry.rb
Error: #<IOError: The required, staged c extension file, "C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/MSPhysics/libraries/stage/win64/2.5/msp_lib.so", is missing!>
C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/ams_Lib/extension_manager.rb:204:in block in require_all' C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/ams_Lib/extension_manager.rb:201:in each'
C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/ams_Lib/extension_manager.rb:201:in require_all' C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/MSPhysics/main.rb:70:in <top (required)>'
C:/SketchUp 2019/Tools/RubyStdLib/rubygems/core_ext/kernel_require.rb:59:in require' C:/SketchUp 2019/Tools/RubyStdLib/rubygems/core_ext/kernel_require.rb:59:in require'
C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/MSPhysics/main_entry.rb:15:in <top (required)>' C:/SketchUp 2019/Tools/extensions.rb:197:in require'
C:/SketchUp 2019/Tools/extensions.rb:197:in load' C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/MSPhysics.rb:21:in register_extension'
C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/MSPhysics.rb:21:in <module:MSPhysics>' C:/Users/Mauro/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/MSPhysics.rb:5:in <top (required)>'

MsP NOT WORKS IN 2017-2020.

Oxer

MSPhysic doesn't work in SketchUp > 2017 but in SU2017 works fine.