SDK is mandatory?

Where it does inserted?

Not mandatory will be installed in it's own directory (sdk=software developer kit)

Don't bother installing the 3.2.3 hotfix. It is only for people with subscription licenses and it fixes their activation bug. If you already installed it, you will see zero difference in P3d except that you might break a 3rd party installer.

 

Could be that you might break something but all 3rd party developers will have to make their products 3.2.3 compatible anyway because the full installer is 3.2.3 by now: you can't download 3.2.2 anymore so everything has to be brought onto the same level. Then again, since the patch only solves activation issues I doubt if it will break anything. 

longrangecruise, on 10 Mar 2016 - 2:17 PM, said:

I updated the client only. Got it to run one time.

 

Now it gets stuck at the blue screen with no progress bar and crashes (after choosing the flight scenerio).

Error ntdll.dll

 

Am not pleased

 

Try the following rename the dll and exe.xml to .off and restart... that way you rule out any third party stuff that isn't compatible

 

 

Thanks André!

I remembered that I installed the updated version 1.32 of the Concorde X before the crashes and uninstalled it. That seems to have fixed it.

I updated the client only. Got it to run one time.

 

Now it gets stuck at the blue screen with no progress bar and crashes (after choosing the flight scenerio).

Error ntdll.dll

 

Am not pleased

 

I had a similar issue after the previous update to v3.1.  I found the information from the P3D forum resolved my issue:

 

"open %LOCALAPPDATA%\Lockheed Martin\Prepar3D v2 then delete 2 files

 

Prepar3D_Default.fxml

Prepar3D_Default.wx"

 

I suggest that you make a backup of the 2 files in case there are issues.

 

**EDIT**

 

I see that you posted while I was searching for the answer to my issue, glad that you resolved your issue.

I had a similar issue after the previous update to v3.1.  I found the information from the P3D forum resolved my issue:

 

"open %LOCALAPPDATA%\Lockheed Martin\Prepar3D v2 then delete 2 files

 

Prepar3D_Default.fxml

Prepar3D_Default.wx"

 

I suggest that you make a backup of the 2 files in case there are issues.

 

That's interesting. See my above post: I just uninstalled Concorde X again and that solved it. Maybe a coincidence...I still have to check with FSLabs or try installing it and deleting the 2 files

 

 

Which in turn need me reinstall global?

And any others?

I just want my gsx working without the possibility of reinstalling it's a headache and time consuming

Any advise guys?

You only need to re-install Global if you un-install re-install P3D scenery.

 

For GSX, update Content and you should be all set.

That's interesting. See my above post: I just uninstalled Concorde X again and that solved it. Maybe a coincidence...I still have to check with FSLabs or try installing it and deleting the 2 files

 

ConcordeX 1.32 works perfectly with P3D 3.2.3 here, so I would look elsewhere.

Been watching this thread, all 485+ posts, off and on. I am trying to follow the logic of all the posts. At first it was claimed that all one had to do was replace the client with the 3.2 client, and everything would work as it did in the 3.1 update. Then I read that one also has to replace the scenery or problems might develop with some add ons. Then apparently content has to be replaced, or GSX won't work, but if one does that, you have to save autogen files and then over write the updated autogen files. Another post said effects needs to be backed up and replaced.  Then some other vendor suggested the only way to make sure everything works, including his product, one should do a total install of 3.2, from scratch and not just update with 3.2. This morning I read that PMDG install has to be repaired in order for Pro ATC to work properly. This sure seems a long way from " Just install the client, and you are good to go".  

 

Whatever happened to the type of update, where you click one icon, and everything installs and works? 

 

 

For GSX, update Content and you should be all set.

 

So reinstalling FTX Global is not required if you only install Client and Content, right? But a backup and copy of the Autogen folder is still required like others have indicated, no?

 

 

So reinstalling FTX Global is not required if you only install Client and Content, right?

Correct.

 

 

 

But a backup and copy of the Autogen folder is still required like others have indicated, no?

I'm not sure on this one.  I didn't do it so I'm not sure what may be broke because of that then.

My advice is to reboot the Universe, and then wait 13.7 billion years until we get to where we are now.

Pablo,

 

I ran into this same problem last night.  After updating content and scenery, I loaded REX4 clouds.  Low level clouds were visible with HDR off, when I turned HDR on the clouds completely disappeared.  I then deleted shaders, created new .cfg, reinstalled REX clouds again, and same thing, however this time there were no clouds with HDR off or on.  

 

Looks like I'll take your suggestion to re-install default clouds.  Thanks for posting your findings.

Hi Brian,

from the rex forum, they are aware of the issue and they're working on a fix.

My advice is to reboot the Universe, and then wait 13.7 billion years until we get to where we are now.

 

   

 

Cheers,

Been watching this thread, all 485+ posts, off and on. I am trying to follow the logic of all the posts. At first it was claimed that all one had to do was replace the client with the 3.2 client, and everything would work as it did in the 3.1 update. Then I read that one also has to replace the scenery or problems might develop with some add ons. Then apparently content has to be replaced, or GSX won't work, but if one does that, you have to save autogen files and then over write the updated autogen files. Another post said effects needs to be backed up and replaced.  Then some other vendor suggested the only way to make sure everything works, including his product, one should do a total install of 3.2, from scratch and not just update with 3.2. This morning I read that PMDG install has to be repaired in order for Pro ATC to work properly. This sure seems a long way from " Just install the client, and you are good to go".  

 

Whatever happened to the type of update, where you click one icon, and everything installs and works? 

 

Bob, I hear you. Take a deep breath and wait for a month for things to settle down. At least, this is my plan of action based on this thread. It seems like 3.2 does not bring any fundamentally functional changes and no show-stoppers for 3rd party developers. Moreover, perhaps it's worth to skip 3.2 all together and wait for other patches.

It seems as there has been another update - we're at 3.2.3 already!