Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
16
Found in
2019.2.0a11
2019.3.0a1
Issue ID
1144436
Regression
Yes
'Selected texture format 'ARGB 16 bit' is not valid' error is shown after manually baking shadowmask
Steps to repro:
1. Open the attached project and 'ProgressiveLightmappingExample' scene;
2. In the Lighting window press 'Generate Lighting' button.
Expected result:
Lighting is baked without errors.
Actual result:
Following error is shown:
"Selected texture format 'ARGB 16 bit' for platform 'DefaultTexturePlatform' is not valid with the current texture type 'Default'.
0x00007FF6AE31C23C (Unity) StackWalker::GetCurrentCallstack
0x00007FF6AE31F711 (Unity) StackWalker::ShowCallstack
0x00007FF6ACBCF035 (Unity) GetStacktrace
0x00007FF6AEEBC27D (Unity) DebugStringToFile
0x00007FF6AC4383F3 (Unity) TextureImporter::CheckTextureFormatValue
0x00007FF6AC44ACBF (Unity) TextureImporter::SetPlatformTextureSettings
0x00007FF6AEC281BF (Unity) SetTextureImporterSettings
0x00007FF6AEC2690E (Unity) MoveTextureSnapshotsToAssetsFolder
0x00007FF6AEC25328 (Unity) WriteLightingDataAssetJob::Integrate
0x00007FF6AC7EEC16 (Unity) JobManager::IntegrateCompletedJobs
0x00007FF6AEB944D4 (Unity) GISceneManager::Update
0x00007FF6AEB914B5 (Unity) `GISceneManager::GISceneManager'::`2'::tickGIInEditorRegistrator::Forward
0x00007FF6ABBC5419 (Unity) CallbackArray::Invoke
0x00007FF6AC3487EF (Unity) ProfilerCallbackInvoke<CallbackArray,281736>::Invoke
0x00007FF6AC354923 (Unity) Application::TickTimer
0x00007FF6ACBD6555 (Unity) MainMessageLoop
0x00007FF6ACBD8F8F (Unity) WinMain
0x00007FF6AF855512 (Unity) __scrt_common_main_seh
0x00007FFBF7FC3034 (KERNEL32) BaseThreadInitThunk
0x00007FFBFA9B1471 (ntdll) RtlUserThreadStart"
See attached vide and Editor.log.
Regression introduced in 2019.2.0a11.
Notes:
- Reproducible in 2019.3.0a1. 2019.2.0a11, 2019.2.0a11;
- Not reproducible in 2019.2.0a10, 2019.1.0f1,
- Reproducible on Windows and OSX;
- Reproducible when baking lighting manually; not reproducible when auto-baking lighting;
- Reproducible only with Shadowmask light mode; not reproducible with Subtractive and Baked Indirect.
- Reproducible when baking with either CPU and GPU PLM and Enlighten.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [ChromeOS] Pixelbook can switch to portrait orientations which result in vertical resolution that cannot be undone
- Compute Shader with RWBuffer<> type throws an error when it is compiled with Vulkan API
- [Device Simulator] When simulator window is narrow, toolbar controls deform and some become inacessible
- [Device Simulator] Only one Touch Input is recognized when using Device Simulator
- "PropertiesGUI() is being called recursively" warning produced when trying to open color picker when object picker is opened
mayasarii876
Mar 09, 2022 05:10
http://103.56.148.201/
http://103.56.148.201/newmpo
http://103.56.148.201/mpo17
http://103.56.148.201/mpomm
http://103.56.148.201/mpotower
http://103.56.148.201/parisklub
http://103.56.148.201/juraganslot
http://103.56.148.201/mpo500
http://103.56.148.201/mpokick
http://103.56.148.201/mpoyes
http://103.56.148.201/xyzklub
http://103.56.148.201/betmpo
http://103.56.148.201/ogslot88
http://103.56.148.201/hoki777
http://103.56.148.201/mpojuta
http://103.56.148.201/299slot
http://103.56.148.201/mpo188
http://103.56.148.201/mpogacor
http://103.56.148.201/mpo300
http://103.56.148.201/rgo365
http://103.56.148.201/kingdom288
http://103.56.148.201/wigompo
http://103.56.148.201/mpo8899
http://103.56.148.201/mpopelangi
http://103.56.148.201/mpo555
http://103.56.148.201/dutampo
http://103.56.148.201/klik368
http://103.56.148.201/388hero
http://103.56.148.201/19dewa
http://103.56.148.201/mpoxl
http://103.56.148.201/mpoas
http://103.56.148.201/mposun
http://103.56.148.201/qqslot
http://103.56.148.201/mposport
http://103.56.148.201/dewa234
http://103.56.148.201/mesinmpo
AndersMalmgren
Feb 16, 2020 20:59
Also this introduces bake artifacts so its a showstopper, needs resolve ASAP
AndersMalmgren
Feb 16, 2020 20:58
Guys you need to backport this to 2019.2.x and 2019.3.x.
Ryan-Hayle
Feb 14, 2020 19:12
Same issue in 2019.3.1f1
AA-Matt
Feb 08, 2020 00:42
Reproduced in 2019.3.0f6 (official stable release)
lazylukey
Jan 24, 2020 20:08
Is this not going to be fixed for 2019.2 and 2019.3?!
Comafly
Jan 20, 2020 07:48
Reproducible in 2019.2.17f1
PHILSA's solution of disabling 'Compress Lightmaps' still works for solving the issue.
sameng
Nov 28, 2019 21:56
Reproduced in 2019.2.13f1
zetaFairlight
Nov 27, 2019 16:28
Reproducible in 2019.2.13f1
GianLucaSacco
Nov 17, 2019 05:16
Reproducible in 2019.2.11f1