Invisibull
-
Posts
599 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Invisibull
-
-
Support Ticket #143755 was put in on 8/27 and so far I've been asked to check a bios setting to see if my RAM was being overclocked (it wasn't). Very disappointing to be completely ghosted by ED on this issue.
-
I'm still getting this crash, but never when using the non-MT .exe. I have reinstalled DCS from scratch am using no scripts or mods, and I have done tests on my memory and it is fine. Could someone please help?
I've attached the latest DCS.log and here is the Windows Crash Report from the Event viewer:
Faulting application name: DCS.exe, version: 2.8.8.43704, time stamp: 0x64e3b9dd
Faulting module name: VCRUNTIME140.dll, version: 14.34.31938.0, time stamp: 0x023b235f
Exception code: 0xc0000005
Fault offset: 0x000000000000165e
Faulting process id: 0x4e38
Faulting application start time: 0x01d9d62a3dcb6612
Faulting application path: D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: d8dd710f-9880-4cdb-a0d4-5a185a6ec61cThx
-
Thx for your reply. I've come to discover that the crash doesn't happen when I'm not using the MT exe. Further, even while using the MT exe it only seems to happen in that particular mission so far. Incidentally, those script errors have been coming up for years in some cases and have never manifested in any noticeable way in the game environment; I don't think they are involved at all.
Thx again.
-
Aircraft used here is an F-16 in MP. Please find relevant logs attached. Thx.
null
-
6 hours ago, Flappie said:
Thanks for your feedback.
You're welcome
-
Yesterday's update has resolved this issue. Thx for all your help, @c0ff
-
1
-
1
-
-
4 hours ago, c0ff said:
Looks like the same issue as here:
Please, try the workaround and report.
This did not help.
-
I've always run all DCS.exe's as admin and there is no Debugging Tools folder, so I'm still feeling the pain over here.
-
1
-
-
I should add that the server will run, but that it takes 3 or 4 hours of "loading" before it will. This was the case even before the hotfix and before I updated Windows.
-
2 hours ago, Sh4rk said:
After your previous report, I tried changing all sorts of regional setttings and input methods on my PC (OS is already English).
Didn't work, even though I set everything to just English, United States and US Keyboard with default date formats etc.
So the cause can't be exactly the input methods even though it may be related to something like language and regional settings, -or- some 3rd party component that's installed by other applications including Google IME.
On the other hand, one other player that was having the same problem, in Discord, said it worked for him after he updated Windows 10 to version 22H2.
Which version is yours? If you want, or can, try updating to 22H2 to see if it fixes the problem.Updating to 22H2 didn't help.
-
1 hour ago, Sh4rk said:
If you want, or can, try updating to 22H2 to see if it fixes the problem.
Trying that now. Thx. I'll report back here when done.
-
I guess the fix wasn't so hot. So, we wait until the next update and hope for the best?
-
@BIGNEWY Today's hotfix had no effect on my issue. The DCS Log is exactly the same and the DCS server is still stuck in the loading screen.
-
8 hours ago, BIGNEWY said:
Things to try,
run a repair on the server / client
rename the saved games dcs folder for the build ( use it as a backup )
restart and login and test.
Hi,
I started by doing all the things you've suggested plus a system restore and none of it helped. I then did a full uninstall, deleted all folders associated with DCS, including the DCS folder within my saved games folder and then did a reinstall from scratch. None of that changed anything either. As far as a "full" log - I provided the entire log in my first post. I'd imagine its brevity is due to the fact that DCS hangs up before a longer log can be generated. DCS is running fine on my PC, but I haven't been able to host a server using the dedicated executable on my server PC since the update.
-
10 minutes ago, COQQ said:
I changed the language setting to Japanese and it still crashes, so I am reinstalling it now.
Best of luck, but reinstalling did nothing for me.
-
1 hour ago, Sh4rk said:
It's not just servers, I'm also having that problem as a client!
DCS won't load no matter what!
Thanks for your reply. Since I did a full reinstall and others seem to be having a similar issue, I think it's pretty likely that today's update is the cause. Hopefully, there's a fix already in the works.
-
23 minutes ago, western_JPN said:
Hi, Invisibull.
I experienced similar crashing on my PC (mine is DCS World 2.8.2.35632 ob client; instead of its server), the final log line is the same about /bin/CockpitBase.dll .
I reported my trouble in another topic
Temporary I switch Windows 10's Language setting into English / United States from Japanese / Japan, then the crashing was solved.
If you can try to change your Language setting of the Windows , test it, even not good solution though ...
Unfortunately, this made no difference for me. Thanks anyway.
-
Hi folks,
I updated my openbeta server today but then when i went to run it the first time, i inadvertently closed it before it had fully loaded. Now it gets caught in the loading screen and hangs there indefinitely. I have uninstalled/deleted everything and tried to start over from scratch, but it's still happening. The log it generates is not very long so I'll just paste it here:
Quote=== Log opened UTC 2023-01-25 21:04:05
2023-01-25 21:04:04.805 INFO APP (Main): Command line: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin/DCS.exe" --norender --server
2023-01-25 21:04:04.805 INFO APP (Main): DCS/2.8.2.35632 (x86_64; Windows NT 10.0.19045)
2023-01-25 21:04:04.805 INFO APP (Main): Application revision: 215632
2023-01-25 21:04:04.805 INFO APP (Main): Renderer revision: 23817
2023-01-25 21:04:04.805 INFO APP (Main): Terrain revision: 23783
2023-01-25 21:04:04.805 INFO APP (Main): Build number: 276
2023-01-25 21:04:04.806 INFO APP (Main): CPU cores: 4, threads: 8, System RAM: 16327 MB, Pagefile: 16384 MB
2023-01-25 21:04:05.004 INFO EDCORE (Main): (dDispatcher)enterToState_:0
2023-01-25 21:04:05.004 INFO Dispatcher (Main): 2023/1/25 16:04 V1803061700
2023-01-25 21:04:05.013 INFO ASYNCNET (Main): ProtocolVersion: 313
2023-01-25 21:04:05.015 INFO ED_SOUND (Main): Using driver: dummy
2023-01-25 21:04:05.015 INFO ED_SOUND (Main): Found 0 available audio device(s):
2023-01-25 21:04:05.015 INFO Dispatcher (Main): InitLow
2023-01-25 21:04:05.204 INFO EDCORE (Main): Loaded C:/Program Files/Eagle Dynamics/DCS World OpenBeta Server/bin/CockpitBase.dllAny help would be greatly appreciated. Thx.
-
1
-
-
16 hours ago, NineLine said:
Anyways, they used the current Open Beta version and reviewed the current roll inertia using a FSSB stick with the force settings set to roll of 8.13 lb and pitch of 11.65.
With these settings T-Day was very happy with the results and felt it was quite accurate.
Frankly, when I compare the above hearsay (we certainly have no way of knowing exactly what "T-DAY" said and what the context might have been) to the account from the Semper Viper! article, it's not even close which of the two should be more heavily weighted as a useful source to answer our inertial roll question. Here's the relevant excerpt from that article:
QuoteWith a conventional flight control system, we simply decrease the amount of stick deflection. In order to accomplish this, we relax pressure on the stick and allow the self-centering forces to move the stick closer to center (i.e., less aileron deflection), thus slowing the roll rate to what we want; then apply sufficient pressure to keep the stick at the new position. This relaxing of the pressure will normally go to zero momentarily, and with the F-16 this is sufficient for the self-checking feature to stop the roll rate completely. (Remember — you don’t have direct control over the amount or direction of the control surface deflection.) The roll rate deceleration is ALSO rapid, so your body and hand tend to couple with the aircraft motion and probably make stick inputs that weren’t intended.
Currently, nothing I can do with my FSSB stick will "stop the roll rate completely" as described in the above article. Also, when I do try to stop the roll now, the response is anything but "rapid." No disrespect is intended here, but I spent the last couple of years really enjoying how well I could stop the viper's roll on a dime and now I'm being told that that behavior was incorrect all along even though we have direct quotes from the horse's mouth verifying that it was perfectly fine in the roll regime (at least from a FSSB user's perspective) before the FM update a month or so ago.
-
3
-
-
On 7/26/2022 at 2:01 PM, NineLine said:
I know our SME is going to have a look as well, and we do have some more FM tweaks coming. Wags did test with a FSSB stick and sees no issue, but he was testing on an internal build, so possible its fixed internally.
Did that internal build not make it into today's update? It def feels different to me. Maybe a placebo effect. I'm sure others will comment shortly.
UPDATE: Upon further testing, I guess it hasn't changed as much as I first thought.
-
1
-
-
Today's update seems to have improved this issue.
-
1
-
-
2 hours ago, Blaze1 said:
This relaxing of the pressure will normally go to zero momentarily, and with the F-16 this is sufficient for the self-checking feature to stop the roll rate completely. (Remember — you don’t have direct control over the amount or direction of the control surface deflection.) The roll rate deceleration is ALSO rapid, so your body and hand tend to couple with the aircraft motion and probably make stick inputs that weren’t intended.
This is exactly how it was with my FSSB until a couple of updates ago. I know it might sound a bit daft, but I really miss that aspect of flying.
-
2
-
-
3 hours ago, NineLine said:
I know our SME is going to have a look as well, and we do have some more FM tweaks coming. Wags did test with a FSSB stick and sees no issue, but he was testing on an internal build, so possible its fixed internally.
If Wags is saying that, then I have faith that it's already fixed. thx.
-
9 hours ago, SCPanda said:
I have FSSB R3L which is force sensing like the real Viper stick. I still feel VERY strong roll inertia after the FLCS update. Before the FLCS update, with my FSSB, the jet stop the roll immediately after I let go (putting the pressure off) of my stick.
Same here. I don't understand how ED can say "Correct as is" in 2019 with no roll inertia, but now say the same thing with lots of roll inertia? It defies logic.
-
1
-
Sight Range Dial Doesn't Move
in Bugs and Problems
Posted
When not caged, my understanding is that the dial should move to reflect the range to a target based on radar returns. I've messed around with this for an hour and have yet to see the dial move off of 1800'. When I cage it, it goes right to 600', but right back to 1800' when uncaged again, regardless of how far away the target is.