Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
And before you respond;
No, I have no mods installed
Yes, I did a clean reinstall, twice(as directed)
No, it's not muted
This is an issue with roughly 6 or more objects. If you're making roads out of mesh puzzle pieces (I am working on making, to hand out to mappers in the future for cities), and frequently need to rotate or possibly undo if slopes aren't right (if you don't do the entire run of the slope at once, which I *TRY* to do because of bug), then you can hit this bug quite OFTEN.
This is also possibly the reason things don't always save correctly for me, a bug which I haven't been able to trace before but possibly can in the future.
@Nadeox1 this is the same map I've been posting about in the development thread, the city I am making, but this has also happened before in Roane County with enough objects selected.
The system is not low on memory or defective in any ways, it's the code in the forest brush editor ever since the new forest brush format was introduced around alpha 0.9 or so maybe almost 18 or so months or 2 years ago? I've been trying to catch this bug for a dog's age and I've finally been able to re-create it. Definitely happens with about a dozen and half or more objects selected, but again can happen with as few as 6+ regularly. Sometimes you have to undo twice or 3 times in a row to get it, and will not always show until you again try to move the objects.
Happens even when the only mod I have is my two maps I am working with at the moment.
If it was only a one-thing, then you can ignore.
If it happens every time, you should check with no mods enabled.
Support ID please.
https://wiki.beamng.com/Support#A_developer_asked_for_a_Support_ID
I said multiple times, we are very well aware of most of the issue the editor has, and we understand it can become really frustating to work with it (heh, imagine our level artist :) )
I please you to keep all this discussion in one place, because it makes really hard for us to track them if it's scattered all over the place and across different forums.
https://www.beamng.com/threads/forest-editor-crash-on-object-placement.55430/#post-876056
That's usually caused by broken mods.
Disable all of them and check again. If persists, do a clean reinstall: https://wiki.beamng.com/BeamNG_FAQ#How_do_I_perform_a_clean_reinstall.3F
Replied in the thread you made (please post only in one place)
If you play on PC that is below the minimum game's requirements, there is not much to do :\
37949
The game does not seem able to initialize the audio device.
Usually reinstalling the audio drivers fixes this kind of issue for most users. You can find the drivers on your motherboard download page.
Please continue in the thread that you previously created, thank you!
Not sure what you mean by 'Near Light Texture', there's no such thing as that.
Possibly you mean the way the lights are 'aimed' on those cars (aimed too high, so they don't light up the floor near-by). Please report that in the dedicated Exporter thread on our main forum, or the Automation forum :)
If you have any programs that puts overlay on the game (Discord, MSI Afterburner, and so on), disable the overlays. Else try using Borderless mode instead (enable borderless mode, then select 1920x1080)