Hotfixes, updates
All possible hot fixes and updates
8 topics in this forum
-
Pinned topics
-
- 0 replies
- 81498 views
-
Topics
-
- 9 replies
- 7550 views
-
- 0 replies
- 3610 views
-
- 1 reply
- 5607 views
-
- 1 reply
- 4415 views
-
- 4 replies
- 7265 views
-
- 0 replies
- 51232 views
-
- 0 replies
- 15529 views
-
Posts
-
By kemp wright · Posted
All: I hate to tell you this but I completely uninstalled Prepar3d 4.5, and I mean completely, every file that referenced the program. I also went after all the CRJ files. Completed reinstall of Prepar3d 4.5, activated it, booted it up and then closed it. Installed CRJ Pro and look at this: I did not touch windows..... Hans, thank you for your patience and assistance in getting me back up and running...!!! -
-
The file system is not case sensitive. And now, we end the discussion here, otherwise I or Aerosoft send you an invoice about that. When Justsim is not „hurry with this“, then simple don‘t pay them for it (for you: don‘t buy there product). So last: no more questions about Sode internal issues and other product files here. For the moment, I look this topic. -
yes, there is a tag there(below under the spoiler I posted more .xml code). yes, but they are not in a hurry with this, and I myself am interested in finding a solution, thanks for helping. it is interesting, it looks like it really is so but not in all cases, a riddle... I changed only: LTAI_SVET to LTAI_Svet2 and now there are no warning now: --- but why then no warning for LTAI_SVET, because the naming(letter size) is different(.xml=LTAI_SVET, SimObjects=model.LTAI_Svet)?: -
Since posting uninstalled envtex and improves with default shaders . A little bit more testing and with or without envtex the EFB dims at dawn and dusk . Envtex makes it worse but not sure it is the root cause . Default I see the same thing but a bit more readable . Unfortunately I tend to set up flight at dawn because that when I like to depart.
-