Ventana software support forum

I have a SD model that can be used for management control and tactical/strategic planning etc. by a large number of actual instances of the one system type. Differences between those instances are believed to be confined to their input data. The question arises: for how many instances should the mod...

Venext.c val[2].vec->vals, (1128) val[3].val, (1129) 1>c:\vensim\venext6\external sub functions\hospital\venext.c(1128): warning C4133: 'function': incompatible types - from 'COMPREAL *' to 'float *' 1>c:\vensim\venext6\external sub functions\hospital\venext.c(1129): warning C4244: 'function': conve...

I am a registered user of DSS v8.1.0. I need to access the sample venext.c file, but cannot find it on my hard drive. Could you please tell me how to access it, or copy it to me at abbeylane21@outlook.com.

There is a model that applies to all instances of the system type modelled. Differences between individual instances are entirely attributable to input data (numbers). In this situation what will constitute sufficient validation in terms of the number of individual instances validated? One instance;...

When you earlier recompiled the DLL for me I was using Visual Studio 2008 and DSS version 7.2. Now I am using VS 2017 and DSS v8.1.0. After implementing advice in the past 24 hours from Administrator Tomfid, I have advanced to 'External function version mismatch need version 62051 (got 62050)' for o...

I am using Vensim DSS v8.1.0 with Visual Studio 2017 in Windows 10. Do I still have the option of writing subprograms in MS C? Or, must they be written in C++? When I double-click on the Vensim icon on the desktop I get a message (before any model is loaded): External function version mismatch need ...

I included _VDFX in preprocessor definitions. No improvement resulted. I have looked at the template venext.c in c:\users\... Many choices and decisions will need to be made, in aligning my existing venext.c with the new one. I would not feel confident in making those choices and decisions. Can you ...

I defined VDF and _VDFX in venext.c and recompiled the DLL. Those definitions made a negative difference to the outcome: 'the external functions in [the DLL] could not be loaded'. I was shut out, until I stated that the DLL should not be loaded next time. Should I remove the above definitions, or do...

_VDFX is mentioned in the Vensim context only in platform_specific.h. In this file _VDFX is defined only #ifdef _WIN64. I am not using WIN64, as far as I know. Each of my applications has a dedicated venext.c. Beyond those I am unsure which is the file that is shipped with Vensim. I have selected a ...

Vensim.h is apparently the only Vensim-type header file in my subprograms. I made the latest version of vensim.h available to those subprograms. When I recompiled the DLL I got error C2039 in venext.c: 'tot_vol' is not a member of 'tag_dim_info_vdf'. 'tot_vol' is in static void validate_vector_arg(V...

Thank you for responding. I deleted the DLL address in tools>options>startup, then exited Vensim. I recompiled the DLL. When I re-entered Vensim the 'mismatch' message had disappeared. It had previously occurred when I double-clicked on the Vensim icon in the desktop: ie before I tried to load a mod...

I have upgraded to Vensim DSS version 8.0.9 x32. This generates an error message: 'external function version mismatch need 62051 get 51050'. Please advise how to make this go away.

Vensim is using 12.3MB of memory when it displays the memory allocation failure message. My external functions are stable, syntactically correct and with working DLLs. All these models run normally, except on DSS 7.2.

Since I downloaded Vensim DSS v7.2 I have experienced the 'Memory allocation failure - subblock' fatal error when trying to load some of my models. The problem is not a matter of model size. My largest model loads OK. Other, smaller, models, do not. All my models loaded without problem before I down...