Thanks for the info, for the moment only French customers benefit from this update on demo accounts. Other languages will be activated very soon, so please be patient 🙂

Hi Wim,

Unless you post examples, maybe nobody will understand. The mess I personally experienced, is also not for putting to words only. 🙁

What I understand from your description, it could be about the DPI settings on your other monitors (the 100%, 125%, 150% etc. setting), which for V12 are interpreted better than for V11 but meanwhile lead to “irreversible” issues. I can’t even tell how I overcame this, which is (sort of) a matter of restoring stuff in your main environment, while then firing up your demo account for the first time. Yes, I know, this first time is too late now, and you have one opportunity for this first time only. Regarding this, you can PRT ask to reset this and after that best never go to the Demo environment unless you are sure to stay at V12.
That’s great, isn’t it ?

But crucial : any question you might see on the screen at starting up “you can convert one time only” (from V11 to V12) can be reset to a next “one time only”, but you need to ask PRT.

Sorry for the super vagueness in this post, but PRT (support) just don’t know how to deal with this all.
Remember the DPI settings for your case (as it seems), because that is an important change in V12 (not that you see it announced anywhere). This exhibits when you move a chart from one monitor with e.g. DPI at 100% to an other with 125%. V11 can not deal with that and the size of all won’t change, while V12 can deal with that, and the size is rendered as should (I can’t explain this, but just observe what happens). But this gets fixed (somehow) when you later start V11 again then now your charts will have different (font and all) sizes. Now start V12 again and the mess is there.
DPI stuff *is* difficult to solve and in V12 this was done nicely. But it is not backwards compatible (or something like that) for how PRT stores its “saved settings”.

Hi again Wim,

Still I experience similar “spill over” as you talk about. But let me tell about that, which could be helpful if PRT engineers get to read this :

I am not sure what you mean with “install PRT-IG/12 on Demo” – maybe this is because I did not attempt that for my IG account. For IB though, without knowing what “installing” means – see the “Klik hier” at the mouse pointer for launching the old V11.1 version and the large “Start uw platform” button for the now default V12 version. I still face similar issues you describe. But then merely that when I start one and the same account in the other environment (like my account A which always works with V11.1 and which I may start in V12 to test something) and where I never save within that V12 environment – next changes things in my V11.1 environment. It can be details in headings, or contents of lists. It just does something.

I think these issues are very hard to tackle for PRT, although you could try to set up a conversation by means of Technical Reports (via Help) and try to send a TR from before (all still OK) and after (things have changed) and that from there they will see what is going on. Solving it would be another thing, but without the real data it is too hard to grasp for hem (up till too hard to believe). Notice that with the TR data they can see all and from the distance they can also use your template without disturbing you with it.
In the TR you can also put a  link to this topic, so you can easily make things visually clear.

image_2023-10-03_161243032.png

Wim wrote:

I gave up on PRT technical reports. I only make them on explicit request from IG Support.

Another one. 🙁 I wonder when ProRealTime is finally pointed out this situation. Something is digging its own grave here.

Well, Wim, I felt free to talk about the PRT-IB situation because in there undoubtedly things are arranged the same as with PRT-IG : The Live and Demo environment is shared. It is shared for the settings. Thus, e.g. change the dimension of a chart in the one, and if all is right you’ll find back that change in the Demo environment. Am I right ?? (probably not, but read on anyway)
If so, then there is your problem. This obviously can’t be. Btw, I told them a dozen times, and if they now ask me to try something in Demo then I just refuse because the next day I won’t be able to work any more and they will have to restore stuff. On my own initiative I can “rather” switch to the Demo environment, because I think I know what to avoid.

Notice that when I talk about V11.1 vs V12 both Live and switching between the two in the same account, for parts of the platform the same is in order. Just think about those elements (entities) which ARE TO BE the same, like all in ProOrder. This is exactly not the case between Live and Demo of one account, but here other entities are to be the same, like your whole charts and all set up. Just sit back and think how complicated that is … Or, sit back and think about the impossibility to trial V12 and a one time conversion of which I told them from day one that this is never going to work out; be able to do it more often and don’t interfere with the other environment or just don’t do it … That’s why today they offer to do it more often, just because it is needed because of all the issues in V12. And you know, with the somewhat larger account for number of windows, V12 is impossible to use. And when you really want to try, you must have that “initial copy” again (think about all the futures charts which changed for content … (not an issue with IG).

And again it is more bad because while they can’t solve these issues with one larger user (me) because of a lack of commonalities with other users, they don’t hear a single thing from IG users. Keep this in mind. IG users don’t talk to PRT support because they are not allowed to. So once in a while it is me talking about your problems (the users from PRT-IG), because I learn them from this forum. ProRealTime is not looking at this forum (although you think they do). ProRealTime support (which is only minimalistically integrated with ProRealTime herself) is not observing it either.

I was drifting off, right ?
Yes. Your example about the production lines should be digested by PRT. Maybe it speaks to them. All I can do is telling them that my own (company’s) software is 100 times larger and PRT would be one of 100 modules modules in it, with always similarities to the issues PRT encounters. So Yes, we have Test environments vs Production environments. We too have the means to copy the Production database to Test database (and preferably not the other way around). We too have Systems code which has to be shared between the two for obvious reasons (like user data and environmental data (your PC and its possibilities and settings and number of screens)). We too have all, but in a 100 times larger fashion. We too have 1000s of users (which are persons). But there is one big difference : we have zero open issues apart from a possible current one instead of over 2000 issues from one user only (me). And oh, we publish Release Notes by the dozen a day. This is what bothers me most – things which are solved are not even communicated. Your own support department (which exists for IB) does not even know about it. Wat een toko …
Hopeless, actually.

So what we can try to do is see through where which issue emerges and how we can avoid that the next time. I think I wrote it earlier in this topic but scratched it again : learn to live with it because you usually won’t get it solved anyway; Introduce the small pause every 10 seconds on the other production line as well, and accept less throughput. Blame VanderLande for it anyway and eventually sue them when you reached the 1 million loss on revenue after warning them in advance.
Think over what you actually think to achieve, while you know they are incapable of solving things because of the lack of knowledge, people and organization.

Think over why you are actually here and whether it can be so that net you are still better off to be here. Consider to ask the community whether they know how to solve your issue of the day.
Ah wait …

🙂

PeterSt wrote:

Another one. 🙁 I wonder when ProRealTime is finally pointed out this situation. Something is digging its own grave here.

PRT Management may analyse Stats showing reduction in the number of problems submitted by users and announce in their monthly meetings … ‘The downtrend in reported user problems continues, congratulations Team for your hard work, long may it continue!’.

PeterSt wrote:

Think over why you are actually here and whether it can be so that net you are still better off to be here. Consider to ask the community whether they know how to solve your issue of the day.

Well, in the end PRT is a wonderfull playground to do rapid indicator/strategy development, and do some preliminary backtesting. But once you think having found a promising strategy, you better migrate the stuff to more robust platforms with better defined languages. But now we’re leaving the subject of this thread.