Creation of custom modules in FS 17.1.2

Question

question

martin.j asked May 12 2017 at 10:48 AM Matt Long commented May 23 2017 at 2:11 PM

Creation of custom modules in FS 17.1.2

Hi,

I have been looking at a video from one of the distributer trainings about the creation of custom Flexsim modules in the Flexsim tree rather than making my own C++ dlls. Unfortunately I cant seem to get it to work. When I run the applicationcommand("savedefaultviewproject"); it asks me if I want to save the view and collapse and close all trees, but it doesn't create those two essential files in my modules folder that I expected and my new module does not show up in the modules menu on right click.

I will reiterate the steps I have taken and perhaps you can tell me where I went wrong:

1 I reinstalled Flexsim 17.1.2 to a custom location to have total read and write access.

2 I added an empty 'NewModule' folder to the 'modules' folder of the new installation.

3 I then opened Flexsim and in the 'View/environment' tree I created the dev =1 node and successfully activated dev mode.

4 I then added a the new subnode 'NewModule' to the 'View/modules' tree where the other installed modules are listed. Into the 'NewModule' node I added another subnode called 'Installdata'.

5 I now ran the applicationcommand("savedefaultviewproject"); and selected 'yes' to the two popups that asked me if I want to save the view project and collapse all trees and views. Flexsim then worked for a few seconds and returned to normal.

6 I checked the 'NewModule' folder under the installation to see of the two module files had been created, but it was still empty, and when I right click a node and go to the modules menu selection I can only see the installed modules and not my 'NewModule'.

Does this approach still work in Flexsim 17.1.2, and if so can you spot what I have been doing wrong?

Software Version:

FlexSim 17.1.2

custom code modules custom

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2017-05-12T21:47:38Z

Matthew Gillespie answered May 12 2017 at 9:47 PM Matt Long commented May 23 2017 at 2:11 PM

You need to do step 4 in the main tree, not the view tree.

Have you taken a look at our ModuleSDK? You'll find a bunch of resources, documentation, and examples to help you develop a module.

Take a look at the QuickStart.html and ModuleDevelopment.html files in the Documentation folder.

· 7

martin.j commented · May 15 2017 at 8:25 AM

I have now tried following the ModuleSDK, but I didn't get any further.

I created the needed nodes in the main tree instead, but now when I 'savedefaultviewproject' I get the following error and Flexsim locks up:

exception: Exception caught in globalcommand_savebyname()
exception: FlexScript exception: VIEW:/standardviews/savedefaultviewproject

Also Next time I open my development version of Flexsim this error pops up.

Fortunately its only the development copy that appears to be broken.

0 ·

moduleerror.png (5.2 KiB)

Matt Long martin.j commented · May 15 2017 at 2:01 PM

Is your FlexSim directory in a place where you have write permissions? If you have it installed in the Programs directory you'll need to move (or create a copy) it into somewhere like your Documents directory.

0 ·

martin.j Matt Long commented · May 16 2017 at 10:44 AM

Ok I have done a bunch more testing on this topic:

If I use a copy of a Flexsim 17.0.3 or 17.1.2 for my Dev_Version the module creation fails - not in the same way but it fails. But using a copy of Flexsim 16.2.2 I managed to create a new module and the recuired *d.fsx and *.t files were created in the module folder.

I have now copied my new module into my Flexsim 17.1.2 Dev_Version and it works! But its still a bit annoying that I cant create modules in Flexsim 17.

1 ·

Show more comments

martin.j martin.j commented · May 23 2017 at 6:59 AM

@Matt Long

But I am not really using the SDK files... I just read the instructions in the QuickStart.html that explains how to make modules in the Flexsim tree. Correct me if I am wrong, but the SDK is only needed to make custom coded modules in Visual C++ right? There is an option to make modules without using the actual SDK files?

0 ·

Matt Long martin.j commented · May 23 2017 at 2:11 PM

Yes, if all you're doing is adding nodes to the Main or View tree you don't need the SDK files. I'm not sure what the issue could be. If you want to try and get together on a screen sharing meeting we may be able to figure out what's going on.

0 ·

question