lets start with a "we don't like spam bots". (spam content removed)
Posts by SWAT_OP-R8R
-
-
hard to tell
maybe the eventviewer logds show more info
what is shown in the launcher is only launcher related... not displaying the reasons for game crashes
after four hours playing you probably should consider a short break anyways

-
working on the station docking issue
-
dunno if we have such a list somewhere
but we have a list of systems with their stations included
-
which shader did you use?
-
always when docking?
if so then it is related to the landing animation scripts
I tested them all in the past but was not able to reproduce the issue. Only just recently I had such a crash in one specific location.
The crashes seem random and I need to figure out a reliable way of testing the issues.
If its only a crash when docking it most likely is related to this.
I can deactivate the scripts but would only be a temp workaround, not a real fix.
-
And those issues are?
nvm, i just read the other thread
-
entweder die mod ist nicht richtig installiert, wurde verändert oder der char (falls einer existiert) ist defekt
-
looks like running
-
-
-
Todays update will improve some stuff on earth as well as restore some vanilla content that was overwritten by CF (of course now in better quality).
It also will improve and fix 4 animations scripts.
The next upcoming update (probably sunday) will then get the work on Kusari assets finished.
-
-
which shader was the problem?
-
anyone else with this issue?
-
I once more changed mission 1.
Players by default start with 0$ now. Only by visiting Juni at the equipment dealer the 150.000$ starting money is added.
The popups introduced earlier will remain the way they are.
This new mechanic applies to newly installed CF versions.
Already existing installations still start with 150.000 and also get 150.000 for visiting Juni (total 300.000). Not a big deal. The new method aims to ensure new players do not run into problems. Players with already existing installations can consider this a bonus payment if they wish.
Technically it is too complicated to remove the 150.000$ from already existing installations due to windows security settings.
Similar changes were applied to OpenSP. You just won't really notice the moment the money is added.
The adjustment to OpenSP was required to prevent conflicts with the normal SP changes. (no other reason).
Main goal of all the changes simply was to give new CF players a butter smooth start into the story without and risks of messing up something.
-
try again
I was just updating that file
probably you just launched when the file was uploaded
-
Quote
I can see how trying to code for each eventuality would be quite complex, not knowing the mechanics of the framework you are working within, I didn't give this any thought. Sorry.
I know how the mechanics work. I just don't know how creative the players are avoiding mission triggers.
I'll try to implement fail triggers soon, but this is going to be a step by step process without guarantee that ill be able to cover everything.
There only should be one or two long missions in Altair and inner core space
-
Assuming you mean an RTX3060 it is only marginally weaker than my RTX 2070 Super. This by no means can explains drops to 21FPS.
Below you can see what I managed to reproduce on my tries.
The 75FPS is locked due to the refresh rate of my monitor. Assuming yours is 60FPS this should be the target in full screen mode with with the DX10/11/12 shader option.
Also assuming you mean these stations below... they render fine for me on a fresh install.
The very last pic shows unlocked FPS in window mode. 160-170 seems to be normal for me at least.
I can only do a few assumptions.
1. It could be a faulty driver on your PC. I suggest using DDU to completely uninstall the graphic driver and then install the newest version directly downloaded from Nvidia. IF that fails you can also try an older driver version (maybe the newest is bugged)
2. try a different shader option and see if you can reproduce exactly the stuff you showed in your screenshot on Neutro station. Maybe a different shader (from the launcher options) leads to different results.
3. Try if running in window mode leads to different results.
4. reset the shader cache and set it to unlimited size reset shader cache nvidia - Google Suche
5. reset the nvidia options to default
(do step 2 + 3 + 4 + 5 prior messing up drivers)
-
more than sufficient