Ventana software support forum

Clicking or double-clicking on any of the warnings or the alleged error does nothing to find out how to resolve the problems behind the messages. No unmatched comment can be found at, before or following line 7960. There is a lack of support for purposes of resolving whatever problems exist. _______...

I have a .dll that compiles without error in both Debug and Release modes. The model is also OK. However, when I run the model in Vensim DSS I get an assertion failure within the .dll. The reason for this is proving difficult to track down. Can I use the Visual Studio debugger while running the mode...

I have followed your advice. Before saving I selected 'Save to file'. Resulting problems include: no indication of the saved file's name, or where it is located.

I right-click on 'Document'. Then I select necessary options. Finally I click on File>Publish. I do not know about 'copying the sketch'. No graphs or tables are involved.

I document a Vensim (DSS) model in order to generate a MS Word version of the Vensim output. I then use that output to create or update a MS Word file of all parameters and variables in the model. In the quite long time since I last completed that exercise something appears to have changed. I am now...

Thanks for your advice. The problems appear to have been resolved.

I have now located a 'define' of DBLPREC (and DPMATH). It is located in vensim.h. The define is as follows. #ifndef _VENSIM_H_ #define _VENSIM_H_ #define DBLPREC #define DPMATH Vensim.h appears at the start of each '.c' suprogram, such as the following. #line 1 #include <assert.h> #include <float.h>...

The DLL was 'usable' in the sense of being error-free in Visual Studio terms. I was previously unaware that 'check model' is governed by DBLPREC.

The instructions provided by you in an email dated from some years ago. I have been unable to relate those instructions to the content of project properties in Visual Studio 2022. I have no desire or intention to waste your time or mine on these matters. Nevertheless, I do need additional advice in ...

With a usable DLL I get an error when I use 'check model' in Vensim. error: missing a closing parenthesis on a lookup table call { parameters } ACLSD[DCCT,DSCP,BSNS]=INITIAL(OPENWF(DCAT,DISC,DEPT,MODEL,1,2,RUNOP[OLS1], OLIST,RECLN,RUNNO))~ ND ~| The error is located after the first argument in the s...

I need to define DBLPREC. Please let me know where and how to do that. '#define DBLPREC' in one of the '.h' files did not work.

MACRO: NORMRN(MEAN,STDV)
NORMRN = RANDOM NORMAL(-1e+020,1e+020,MEAN,STDV,0)~~|
:END OF MACRO:

I have previously used the above format in my Vensim DSS models. Now it is not being accepted. Please let me know the revised format.

John Weldon
abbeylane21@outlook.com

Some changes to Vensim are disruptive and extensive. 'COMPREAL' is the most-recent example. Currently, users are provided with a template project, and are then expected to rebuild their own projects from scratch. There are various circumstances and reasons why this approach is undesirable and even s...

Some changes to Vensim are disruptive and extensive. 'COMPREAL' is the most-recent example. Currently, users are provided with a template project, and are then expected to rebuild their own projects from scratch. There are various circumstances and reasons why this approach is undesirable and even s...

By 'the function' I assume that you refer to the subprogram: in this case paramid4.c. I changed its declaration to COMPREAL /*FUNCTION*/ PARAMID4( ... The declarations of function PARAMID4 in venext.c are extern COMPREAL PARAMID4(DATAP INVAR, DATAP ONDTM, DATAP OSTTM, DATAP XNDTM, DATAP XSTTM, COMPR...

One type of warning that appears often is 1>c:\vensim\venext6\external sub functions\hospital\paramid4.c(663): warning C4244: 'return': conversion from 'COMPREAL' to 'REAL', possible loss of data COMPREAL paramid4_v; if( EQUAL(type, ONE)){ // integer array paramid4_v = (COMPREAL)entout4[ndm1 - 1][nd...

I changed all extern REALs to double, to conform with the sample venext.c. That did not work. Same warnings as before. I then changed all extern REALs to extern COMPREALs. That did not work either. Following your latest advice I changed all internal REALs in ADJTM.c to COMPREAL. In venext.c (extern ...

I always welcome simple solutions. However, there are apparently no REAL instances to replace in venext.c, particularly in the 'case' section of venext.c where all the COMPREAL warnings occur. Am I misunderstanding you in some way?

It is not sufficiently evident from the sample venext.c what the new version of my ADJTM.C etc. should look like. I should therefore be obliged if somebody could translate ADJTM.C into that new version. I could then use the 'template' to convert the remaining 130 plus instances. In my models an exam...

For my work in developing models 32bit will probably always suffice. My objective has been to confirm that one particular application will run under Vensim 8.1 and Visual Studio 2017. When that application is used by others the 64bit version may be needed. I have not yet tried to run the application...

Reference 'tomfid' Your first paragraph has already been contradicted -- by a previous one-off or particular allocation of additional memory to another user. I am not asking for a generic anything; only the same treatment as that provided to the other user. Your second paragraph seeks to ignore the ...

I received files from the administrator on 9 April 2020. Those files would then have been processed for use as external function subprograms and compilation into a DLL. The error message 'memory allocation failure - subblock' appears when I try to load a model into the Vensim screen. The message mea...

With reference to 'administrator' It is impossible to remove all calls to subprograms. But, as many of them as possible were removed, and those calls remaining are also made in the two smaller models. Those use the same DLL and run without problem. In that sense the answer to your question is 'no'. ...

With reference to 'tomfid'. I am using x86 (32 bit). In my experience life has become more difficult the higher the Vensim edition (from about v7.0). I do not wish to change editions until the memory allocation failure problem has been resolved. The same problem for 'rossen' was evidently resolved w...

On Tuesday 7 January 2020 'rossen', a registered member of the Vensim forum, reported that he was experiencing the error message 'Memory allocation failure - subblock'. On the same day the forum's administrator responded: 'I'll see if I can enable more memory for this'. The administrator was not ask...