• 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.

startup error

Hi,

I think (or hope) that I have finally fixed this problem. I think it was an issue with my C# projects and how some x86 and x64 settings were mixed. With the move to .NET 4.0 I changed the build server and that's why it gave trouble.

New development release will be online in 10 minutes or so. Let me know if it works for you as well :)
 
just tested 24/1 release, still crashes :oops:

edit...
crash is repetitive, scenProc will not run at all now on my station
it loads and crash every time; with exactly the same error messages i posted before
 
Last edited:
Humm, this is driving me crazy. I can't properly reproduce it in the IDE and there is no proper stack trace to give an indication of where the error occurs.
 
Hi,

Did some more research and it seems the text editor control doesn't work well under .net 4.0. I'm going to try to update it soon. As a result memory gets corrupted now, hence the random crashes.
 
Just to add to this discussion. I've been seeing frequent scenProc crashes. Since I only started using the tool about 4 days ago I've only been using the last 2 versions. Both versions seem to crash sometimes. I've had crashes mostly when opening the tool, and sometimes when trying to use the "New" Button.

I thought it could be my setup because I don't have FSX installed on the machine where I run scenProc, and I point the P3D folder in settings to my network mapped drive where P3D is. Seems like that isn't the issue though as others are seeing crashes too.

Once I get it working (usually by creating a new config/trying to open a few times) it runs nicely and hasn't crashed while processing yet.

I'm using Windows 7 and have .net 4.5.2.

Hopefully this info may help a bit :)

Screen Shot 2015-01-25 at 14.00.51.png
 
MyPC8MyBrain said:
you traced it?... W00T :wizard:

just an FYI, .NET4 was retired and is replaced by 4.5
Click to expand...
But .NET 4.5 is not available for Windows XP and there are still quite some users of my tools that use XP. So that's why I settled on 4.0.
 
I did a little survey a few weeks ago and there are too many users still on XP to ignore them.

Although I think most of them are MCX users. But since my tools share components I prefer to use one .NET version.
 
If the start-up crashes continue any thought to an "XP" .NET4.0 version and a "P3D .NET 4.5" version? Though, I am sure if there is anyone who can find/fix the current issues it is you, Arno. Really appreciate you plugging away on this.
 
The text editor control doesn't work with .NET 4.5 either. Only with older versions. But I think I can fix it, just haven't had time behind my development PC yet.

I'll never make two versions with different framework versions. That would just complicate development, testing and debugging too much for me.
 
I'm very happy with such active users that support the development.
 
Hi,

The error should be fixed now, the new development release is online.

The issue was somewhere in the mode of the text editor control that allows you to enter Japanese and Chinese characters. So I just disabled that, as I don't think it's important for scenProc (didn't even know that mode was there before now).
 
You must log in or register to reply here.
Back
Top