Julean

Are your P3D v4.0-1 working? Mine has been down for weeks because of .NET CTD

Recommended Posts

We are some who are fighting to get the P3D up flying again. 

Some has uninstalled everything, even Windows for trying to get it to work.. But no - its not working...

In my limited computer understanding, something is wrong between Windows and P3d.

The subjedt on Prepar3D forum https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=127165&p=170409#p170409

But how are your game?  

No .NET Framework problems?

Or has anyone heard of the solution to this?

All the best 

Jens

 

Lognavn:       Application
Kilde:         .NET Runtime
Dato:          09-11-2017 18:37:00
Hændelses-id:  1026
Opgavekategori:Ingen
Niveau:        Fejl
Nøgleord:      Klassisk
Bruger:        I/T
Computer:      Julean-Pc
Beskrivelse:
Program: Prepar3D.exe
Framework-version: v4.0.30319

Beskrivelse: Denne proces blev afsluttet pga. en ubehandlet undtagelse.  = Translated : This process was terminated due to an untreated exception.

Undtagelsesoplysninger: undtagelseskoden c06d007e, undtagelsesadressen 000007FEFD30A06D

Hændelses-Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-11-09T17:37:00.000000000Z" />
    <EventRecordID>45078</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Julean-Pc</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Program: Prepar3D.exe
Framework-version: v4.0.30319
Beskrivelse: Denne proces blev afsluttet pga. en ubehandlet undtagelse.
Undtagelsesoplysninger: undtagelseskoden c06d007e, undtagelsesadressen 000007FEFD30A06D
</Data>
  </EventData>
</Event>

Lognavn:       Application
Kilde:         Application Error
Dato:          09-11-2017 18:37:02
Hændelses-id:  1000
Opgavekategori:(100)
Niveau:        Fejl
Nøgleord:      Klassisk
Bruger:        I/T
Computer:      Julean-Pc
Beskrivelse:
Navn på program med fejl: Prepar3D.exe, version: 4.1.7.22841, tidsstempel: 0x59d67e95
Navn på modul med fejl: KERNELBASE.dll, version: 6.1.7601.23915, tidsstempel: 0x59b94f2a
Undtagelseskode: 0xc06d007e
Forskydning med fejl 0x000000000001a06d

Proces-id 0x13dc
Programmets starttidspunkt 0x01d3597fa5fffca0
Programsti: E:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Modulsti: C:\Windows\system32\KERNELBASE.dll
Rapport-id: 97db5730-c574-11e7-9ff5-f832e4866aa9
Hændelses-Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-11-09T17:37:02.000000000Z" />
    <EventRecordID>45079</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Julean-Pc</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.1.7.22841</Data>
    <Data>59d67e95</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.1.7601.23915</Data>
    <Data>59b94f2a</Data>
    <Data>c06d007e</Data>
    <Data>000000000001a06d</Data>
    <Data>13dc</Data>
    <Data>01d3597fa5fffca0</Data>
    <Data>E:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data>
    <Data>C:\Windows\system32\KERNELBASE.dll</Data>
    <Data>97db5730-c574-11e7-9ff5-f832e4866aa9</Data>
  </EventData>
</Event>

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

1 hour ago, lodestar said:

read the avsim configuration guide and CTD guide, they are just great. 

Also(just a guess), maybe you need some of this https://www.microsoft.com/net/download/windows

I also recomend you installing this http://www.majorgeeks.com/files/details/visual_c_runtime_installer.html

You'll find all this things and links in avsim guides

Iodestar..

Thank you.

That made me updating  with all C Runtime og and repair .Net Runtime. ..

But  still .NET CTD.. 

Jens

Share this post


Link to post
Share on other sites
1 hour ago, Julean said:

That made me updating  with all C Runtime og and repair .Net Runtime. ..

But  still .NET CTD.. 

I'm going to have to remove this "fix" as it only fixed a dotnet problem I was having a couple of years ago and the fix was provided by a computer expert (PaulJ who use to be active here).  It might have fixed someone else's problem but the technology and updates of the dotnets makes the fix less unlikely.  When you have a dotnet error, it is most likely caused by an incompatible module for P3DV4.1.

Look in the dll.xml located in the same folder as your scenery.cfg (it's the default location).  Disable CMeteoXmlx64 module by changing the Disable line from False to True.  This fixed my problem when I got the dotnet error and then the kernelbase error.

If this does not fix your problem (it will if you have the module loaded; it comes with Carenado aircraft), then look in the CTD Guide and following the instructions for fixing most CTD's and Freezes in P3DV4.1.

Best regards,

Jim

Share this post


Link to post
Share on other sites
16 hours ago, Julean said:

Iodestar..

Thank you.

That made me updating  with all C Runtime og and repair .Net Runtime. ..

But  still .NET CTD.. 

Jens

I've just read your error log carefully, and it says "Framework-version: v4.0.30319"

On LM website, under system requirements for current version of P3Dv4 it says you need Microsoft .NET Framework 4.6.2 installed. So, it could be this? :happy:

Here is a link:

https://www.microsoft.com/en-us/download/details.aspx?id=53344

also, check this usefull tool https://blogs.msdn.microsoft.com/astebner/2008/10/13/net-framework-setup-verification-tool-users-guide/

Share this post


Link to post
Share on other sites

Hi Zeljko,

Nice to see you back.  Love your expertise!  All of my P3DV4.1 crash reports show v4.0.30319 but I do have dotnet 4.6.2 installed.  I think an addon is using 4.0.30319 as they are mostly not backward compatible.  I have a super stable computer now that I unloaded the Carenado CMetroXML module when starting P3DV4.1.  It's funny that is causing an issue (at least for me) as it worked well in P3DV4.  Something was changed in V4.1 that causes CMetroXML to cause crashes.  This dll was infamous in FSX and P3DV3 installations for causing crashes and everyone had to remove it from the dll.xml.  Thought Carenando had fixed it with P3DV4.0 but it's not working again.  I have no idea what the module does for Carenado but understand from the FSX days it is not needed.  All of my Carenado aircraft run without an issue.

Best regards,

Jim

Share this post


Link to post
Share on other sites
27 minutes ago, Jim Young said:

I think an addon is using 4.0.30319 as they are mostly not backward compatible

Yes, that should be the explanation. I don't know about this - not using carenado planes.

BTW, i'm here every day, but i didn't have time to post so often,very bussy in the last time

Share this post


Link to post
Share on other sites
2 minutes ago, lodestar said:

BTW, i'm here every day, but i didn't have time to post so often,very bussy in the last time

Hmmmm, lots of golf huh? :biggrin:

Share this post


Link to post
Share on other sites

Thank you very much for the answers, all of you.

 

On 9/11/2017 at 10:49 PM, Jim Young said:

I'm going to have to remove this "fix" as it only fixed a dotnet problem I was having a couple of years ago and the fix was provided by a computer expert (PaulJ who use to be active here).  It might have fixed someone else's problem but the technology and updates of the dotnets makes the fix less unlikely.  When you have a dotnet error, it is most likely caused by an incompatible module for P3DV4.1.

Look in the dll.xml located in the same folder as your scenery.cfg (it's the default location).  Disable CMeteoXmlx64 module by changing the Disable line from False to True.  This fixed my problem when I got the dotnet error and then the kernelbase error.

If this does not fix your problem (it will if you have the module loaded; it comes with Carenado aircraft), then look in the CTD Guide and following the instructions for fixing most CTD's and Freezes in P3DV4.1.

Best regards,

Jim

But now my problem is that my dll.xml file i very little in content!

Xyfx6YF.jpg

Some wonder if this on purpose that the file is so little or even not to be found...?

http://www.prepar3d.com/forum/viewtopic.php?t=125649

18 hours ago, Luke said:

Keep in mind that the .NET framework version and the Common Language Runtime versions are different:

https://en.wikipedia.org/wiki/Common_Language_Runtime

The newest version of the CLR is 4.0, so your error report makes sense.

Cheers!

I don't know how to deal with this? Luke what does this mean?

I have tried to search for CMeteoXmlx64, but the search engines didn't find it. 

Than for for the help

Jens

Share this post


Link to post
Share on other sites
3 hours ago, Julean said:

I have tried to search for CMeteoXmlx64, but the search engines didn't find it. 

I was the one who referred to CMeteoXmLx64.  It belongs to Carenado aircraft.  If you do not have any Carenado aircraft, then it is not installed.  If it is installed, it will be in the same directory as where your Prepar3D.exe is located (the main folder). 

3 hours ago, Julean said:

But now my problem is that my dll.xml file i very little in content!

The dll.xml you are showing is the one in the same folder as your scenery.cfg.  This is the new P3D default location.  Back when P3D was first released, the default location was in the same folder as where your P3D.cfg is located (another hidden folder).  Many developers still use this as the default location.  Looking at the directory you provided I see several addons installed that installed a module in the dll.xml and made a backup copy.  For instance for the CRJ 700-900X.  I do not see the entry in the dll.xml you posted so you have a major mess you will have to sort out.  The entries could be in the dll.xml located in same folder as your p3d.cfg but then the backups would be there and not in the folder where your scenery.cfg is located.

There are also entries in the exe.xml but I have never seen any of those entries causing a crash.

If you have the fsuipc.dll utility installed make sure it is the version fsuipc5.  It is the only one compatible with P3DV4 and payware.  When it is installed, the entry is placed in the dll.xml located in the same folder as your p3d.cfg.

Share this post


Link to post
Share on other sites

 

On 11/11/2017 at 3:29 PM, Jim Young said:

I was the one who referred to CMeteoXmLx64.  It belongs to Carenado aircraft.  If you do not have any Carenado aircraft, then it is not installed.  If it is installed, it will be in the same directory as where your Prepar3D.exe is located (the main folder). 

The dll.xml you are showing is the one in the same folder as your scenery.cfg.  This is the new P3D default location.  Back when P3D was first released, the default location was in the same folder as where your P3D.cfg is located (another hidden folder).  Many developers still use this as the default location.  Looking at the directory you provided I see several addons installed that installed a module in the dll.xml and made a backup copy.  For instance for the CRJ 700-900X.  I do not see the entry in the dll.xml you posted so you have a major mess you will have to sort out.  The entries could be in the dll.xml located in same folder as your p3d.cfg but then the backups would be there and not in the folder where your scenery.cfg is located.

There are also entries in the exe.xml but I have never seen any of those entries causing a crash.

If you have the fsuipc.dll utility installed make sure it is the version fsuipc5.  It is the only one compatible with P3DV4 and payware.  When it is installed, the entry is placed in the dll.xml located in the same folder as your p3d.cfg.

Jim Young you said: 

Quote

 

The entries could be in the dll.xml located in same folder as your p3d.cfg but then the backups would be there and not in the folder where your scenery.cfg is located.

There are also entries in the exe.xml but I have never seen any of those entries causing a crash.

 

Is there a instruction in how I can do LM's job in sorting this out.. 

Why don't LM create cleanup and maintenance programs? That evaluate programs installed into the sim.

And have a blog of the current issues? I mean there are people on the .NET Runtime there has been dragged into deep uninstall and reinstall procedures and to no result and no support.

There seem to be a problem with windows this time.

Time will show. 

Here my Two DLL.xml  

GVpkV7N.jpg

Axzsf65.jpg

 

Thank you.

Jens

 

Share this post


Link to post
Share on other sites

You have problems with your dll.xml's.  The one in your Roaming folder or where the p3d.cfg is located, has three PMDG entries.  They do not belong there as PMDG only uses the default folder (in the same folder as your scenery.cfg).  Only fsuipc 5.dll and as_connect for ASP4 are being installed in the Roaming folder by the developer.  Everything else is being loaded in the new default location.  I have no idea why you have PMDG Options, PMDG Events, and PMDG Sounds entries in the Roaming dll.xml.  Those are from back in the old days.  They might be causing major conflicts when loading.  All dll.xml entries are loaded when you first startup P3D to the Setup screen.

Again, aren't you missing several other entries in the dll.xml Malorca X Evolution says they have an entry as they made a backup of your dll.xml before they added the entry.  Same goes with the CRJ and the other many dll.xml backups you have in your directory.  Supposedly, if you uninstall one of those products, they will replace your dll.xml with the one they backed up.  But there can be major, major problems with that scenario.  I also delete the backups so that won't happen.

If you want those entries for those products in the dll.xml, you will have to reinstall each addon remembering that P3DV4.1 is now using add-on.xml's instead of the scenery.cfg.  Your products should still work in the scenery.cfg but I have had issues in the past if I have an add-on.xml for a scenery and the entry is also in the scenery.cfg.

Best regards,

Jim

Share this post


Link to post
Share on other sites

And just to add to what Jim said, do not make the mistake of thinking that the dll.xml in both locations are copies of each other, they should not contain the exact entries.

  • Upvote 1

Share this post


Link to post
Share on other sites

Thank you. 

I have the registered version of fsuipc5. 

Why didn't p3d do its job of filling up the dll.xml and only write sporadic?

Should I delete the dll's, are they necessary in p3d v4? Especially when p3d can't seem to write the dll's.

Jim Young, I understood that reinstall of scenery would rewrite dll.xml.

Soo should I reinstall all scenery and aircraft for the dll writing?

I really wonder what all this i about. 

Gentlemen if could get you to look at this thread and see how hopeless the .NET errors is to fellow simmers.

They have done everything.  

https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=127165&p=170409#p170409

There is something wrong with windows here, win 7 64 bit and P3d. 

Do you suppot this impression?  

Or too early to say?

Thank you again. 

Jens

Share this post


Link to post
Share on other sites
2 hours ago, Julean said:

Why didn't p3d do its job of filling up the dll.xml and only write sporadic?

Should I delete the dll's, are they necessary in p3d v4? Especially when p3d can't seem to write the dll's.

It's not P3D's job to write to the DLL.XML; it's the responsibility of the add-on installers to do so properly. (This is why P3D has moved to the add-on.xml model; the risk of a misbheaving installer or uninstaller messing up the whole system is apparently too great.)

The error messages aren't surprising. P3D is calling KERNELBASE.DLL with bad data and the kernel is faulting - my guess is that it's likely to do with scenery or some other component not loaded via the DLL.XML.

Cheers!

Share this post


Link to post
Share on other sites
3 hours ago, Julean said:

Jim Young, I understood that reinstall of scenery would rewrite dll.xml.

Soo should I reinstall all scenery and aircraft for the dll writing?

You can delete your dll.xml in both the locations (p3d.cfg and scenery.cfg folders).  Once deleted, when you restart P3D the default dll.xml will be installed (with no entries).  This means you won't be able to use fsuipc5 as it won't load and you won't see it in the P3D Menu because you will no longer have an Addons Menu.  You won't be able to edit or use RAASPRO or FSDT/FlightBeam scenery too as there will be no menu in P3D where you can open up and register the products.

So uninstalling the dll.xml would be a disaster. The dll.xml is probably the most important file that P3D loads when you first start up P3D.  I would rename the current dll.xml's to dll.xml.off.  This is so a new default dll.xml can be created.  Once a default is created, shutdown P3D and open the dll.xml in the same folder as your scenery.cfg.  Copy the following and paste in the dll.xml:

<Launch.Addon>
        <Name>PMDG Interface</Name>
        <Disabled>False</Disabled>
        <Path>PMDG\DLLs\PMDG_Interface.dll</Path>
        <DllStartName>module_init</DllStartName>
        <DllStopName>module_deinit</DllStopName>
    </Launch.Addon>
    <Launch.Addon>
        <Name>RAASPRO</Name>
        <Disabled>False</Disabled>
        <Path>.\RAASPRO\RAASPRO.dll</Path>
        <DllStartName>module_init</DllStartName>
        <DllStopName>module_deinit</DllStopName>
    </Launch.Addon>
    <Launch.Addon>
        <Name>XMLTools64</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>XMLTools64.dll</Path>
        <DllStartName>module_init</DllStartName>
        <DllStopName>module_deinit</DllStopName>
    </Launch.Addon>
    <Launch.Addon>
        <Name>PMDG_HUD_interface</Name>
        <Disabled>False</Disabled>
        <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
        <DllStartName>module_init</DllStartName>
        <DllStopName>module_deinit</DllStopName>
    </Launch.Addon>

Save.   

You should then reinstall fsuipc5 and AS for P3D4.

The fix for the CLR.dll error is to run the Microsoft.net Repair Tool - https://www.microsoft.com/en-us/download/details.aspx?id=30135.  I had the same error yesterday (Sunday) and have not seen the error since then.  It made some changes to address dotnet Framework installation problems and asked me to reinstall the dotnet I was having issues with (v4.0.30319).  I told the repair program I was not going to do that and clicked on Next and it finished up.  I have not had an error since and I have used P3Dv4.1 quite extensively since then as I have been testing for the causes of stutters over Orbx SoCal (fixed it by uninstalling Orbx SoCal as it is the problem).

I know you did this once before but maybe you did something wrong.  You should also open up Windows Update and look in the left column for Troubleshooting.  Click on Troubleshooting and it will repair your registry (but it really won't or at least it hasn't for me but there is an issue with Windows Update for sure and Troubleshooting will "fix it".  That and the DotNet Repair Tool fixed it for me.

BTW, that thread you posted a link to was interesting but it is all useless.  The experts are at AVSIM... :smile:  Tell them to read the AVSIM CTD Guide for more good advice!

Best regards,

Jim

Share this post


Link to post
Share on other sites

First Jim and Luke and others.

Thank you very much taking this effort and spending the time..

Very kind of you guys.

Because of Sebastians trouble (The prepar forum ) in uninstalling practically everything and still not working. I got the impression that this seems to be very deep rooted. So I have spread the word.

Thank you Jim for the dll instruction.. which I will do.

Regards Jens

Share this post


Link to post
Share on other sites

A move towards X plane


Today I had the same .NET Framework errors ... After doing the best, all these gentlemen in the forums had suggest to the best of my ability. But as Sebastian among others have stated.. Even if you install everything, even windows from scratch the problem is still there. 
So the hypothesis of it being a LM Windows conflict is still standing.

Like the others in this thread and the fact I have been a loyal simmer to Microsoft Flightsimulator since.... 2000  
That's 17 years gentlemen.. I am fed up. 

This ongoing game of CTD-work in finding out what's going on.. And the sorry to say, the way LM shuffle their customers especially in this thread and the tread I link to here, have made me to the devastating decision to start op X plane..

https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=127165&e=1&view=unread#unread 

Have I used $4-5000 in 17 years... I wonder?

Today Microsoft came with the update to the win 10 error, but nothing about the .NET framework error.

I have suggested LM to make scanning tools to sort out .cfg files and dll entries and all sorts of entries.

I think maybe I am in a wake up process to move to X-plane.

Share this post


Link to post
Share on other sites

Sorry to hear you are still having problems.  P3DV4 works great "out of the box" and then you add addons and all heck breaks loose.  The fault for your crashes is not LM's P3DV4 but an addon.  Find it (like I did) and all will be well.

Yesterday I upgraded to Windows 10 v1709 (latest and the one version many people had problems with).  It took some time to download and install but P3D works great. 

In my case, I had issues with installing Orbx SoCal (my fault, not Orbx or LM).  It evidently caused the G3D.dll error as I disabled it and no more crashes!!

Do you want to know why XP11 works so well for many and not many are having crashes (actually almost zero crashes)?  Because you cannot install an old scenery or aircraft program made for FSX or FS9 into XP11!!  So, dump all your addon scenery and just have P3D installed in default configuration.  Runs perfectly.  Do NOT install any addons unless you know for sure, 100% sure, the addon works and it was installed properly.

Share this post


Link to post
Share on other sites

Hi Jim

Thank you for your answer. And Jim ,soo much appreciate your help -Thank you again. I have changed the dll.xml as you said. And used repair tools that only changed windows installers.. But have given up on "searching for the needle in the hay stack" the crashing scenery, because the experience by Sebastian.

Quote

Sorry to hear you are still having problems.  P3DV4 works great "out of the box" and then you add addons and all heck breaks loose.  The fault for your crashes is not LM's P3DV4 but an addon.  Find it (like I did) and all will be well.

But at this point you could say this is my responsibility that I don't find the obstructing program.

But on on the prepar3d thread which I have linked earlier e.g. Sebastian have done everything LM asked him to do. He even reinstalled Windows. He really did everything. And from there we learned that it is a problem in P3D or a conflict in Windows to P3D.

On top of this LM have not given him the support or tried to help him. They could say: "Stop struggling we know the problem, wait wait! . we sort it out."

It's just depressing and that level of attitude and this example has exhausted me. Sebastian is very disappointed about LM.

I have have been in this for 17 years and LM have enormous resources. They even building UFOs and using extreme AI not publicly known. :cool:

http://www.collective-evolution.com/2015/06/23/2nd-director-of-lockheed-skunkworks-shocking-comments-about-ufo-technology/

Actually they could do a lot better in maintaining a flight simulator. They way Sebastian was treated was a bad sign in the way they seem to play games with their customers. Well maybe it was a slip from their side, because this is for me a "no go". And well If they are making things difficult they could do it nicely. 

This must be hard against the Add-on developers because X-plane seem to have a much more freeware community. When X-plane develops seasonal textures a cross way is reached. Because now then can implement google maps into the simulator and making stunning scenery that we pay hundred of dollars for in P3D. 

All the best Jens

Share this post


Link to post
Share on other sites

I have exactly the same problem. For me, a Windows reinstallation has unfortunately brought nothing.

I fancy that the first time the error occurred after the TOGA, EDDL Justsim or FSDG Sharm El-Scheikh update. Also possible that it has to do with the AS V4 update, this was also updated during this time by me.

With me, unfortunately, no repair attempts, it does not work with and without addons. It is to despair.

 

regards Steffen Herzlieb

  • Upvote 1

Share this post


Link to post
Share on other sites

Again P3D V4 works for thousands so it's frustrating to hear it's not working for you.

  • Upvote 1

Share this post


Link to post
Share on other sites

Julean did you also install Sharm el-Sheikh? I suppose the problem comes with me from this addon, without it works for me. I also think that the old framework was installed with this app.

Share this post


Link to post
Share on other sites
On 16/11/2017 at 11:36 PM, Steffen986 said:

Julean did you also install Sharm el-Sheikh? I suppose the problem comes with me from this addon, without it works for me. I also think that the old framework was installed with this app.

Steffen.. No I dont have..   

 

On LM Thread I wrote this..:

Quote

 

I got a rude message... after I stated "I try X-plane".. and felt disappointed.. And I share the moving to X-plane post on the LM forum also. 
X-plane is not easy  either.. They seem to have really complicated add-on implementation processes. And I bought som Airbus planes that have lacked updates for a long time.

But I checked forum messages and got this one..

Quote
Quote

 

Board warning issued

Sent: Thu Nov 16, 2017 5:12 pm 
From: Kayla Kinzel 
Recipient: Julean 

The following is a warning which has been issued to you by an administrator or moderator of this site.

Please adhere to the User Agreement. Your post has been deleted.

 

I am not used to gang thug attitude loyalty training. This should not be about violence.. I am seriously trying to sort this out.. and LM should focus on this an not fall to such things. I dont hope I am going to start support at developers on all my P3D v4 add-ons and forum debates about unproportional oversensitive defensive interpretation of attempts at dialogue.

All the best especially to LM..

Jens Michlas.

 

I am not used to such amount of force because of customer dissatisfactions and appeal of support.

Now suddenly LM are creating drama, and it's incredible.

 

 

On 16/11/2017 at 3:26 PM, Jim Young said:

Again P3D V4 works for thousands so it's frustrating to hear it's not working for you.

Yes and for many it s not working..

Now trying this one..

But this turned out that my mscoree.dll are newer than my .Net Framework 2 or 3.

And this one..

This did not help, because I have a newer version of .NET framework than the V.4.0.30319 and the installer will not install this version.

 

 

Now this turns out to be interesting.. 

It looks like I am missing "mscoree.dll" files on my Win 7 64 computer.

Here is my folder: 

iMZ3u8j.jpg

 

Here is the folder belonging to the guy in the video.. 

o034SOT.jpg

 

I must surely miss something.. 

If I miss these files how do I get them?

I will post this last part on the p3d forum as well. 

https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=127165&e=1&view=unread#unread

 

All the best

 

Jens 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now