• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Weird Bugs in VB8 Prof/SP1 w/SimConnect

Messages
64
Country
germany
Meanwhile i've found several weird bugs using VB8/VS8 Professional w/SP1

Here a screenshot while debugging some code. If you look at the yellow line that shows the current position in code and look at the fly over window that tells the contents of the "throwEx" variable then you'll see what i mean: Evaluation of the condition is wrong.

I have the suspicion that this is caused by severe pointer bugs in SimConnect which causes the process memory to be corrupted. I couldn't reproduce this phenomenon in a small test project, but i have at least one more case where something like that happens in FSCareer.

The error doesn't happen in the release version of FSCareer but that says nothing since the corrupted memory just shifts to another location in memory which might produce other random bugs that i didn't discover yet.

Anyone here with similar observations?
 

Attachments

  • VS8Bugs01.jpg
    VS8Bugs01.jpg
    81.6 KB · Views: 555
Believe me, you're not the only one to have problems. I've messed around with managed simconnect using both C# (which I'm terrible at) and VB.net (which I'm great at) and Ive found more oddities than I can count on my fingers.

I'm pretty sure it has to do with the CLR interface, which would explain it's oddities with all of the managed languages. If I were you, I would try it in C++ just to see if it is a .net thing.

Here's to hoping the next simconnect is bug-free!

Sean
 
Back
Top