# \*TEMPERATURE doesn't work with \*BUCKLE **URL:** \ **Category:** Bug Reports\ **Created:** [October 16, 2022, 10:19am UTC](https://prepomax.discourse.group/t/temperature-doesnt-work-with-buckle/455 "2022-10-16T10:19:49Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![FEAnalyst](https://yyz2.discourse-cdn.com/free1/user_avatar/prepomax.discourse.group/feanalyst/32/688_2.png) [@FEAnalyst](https://prepomax.discourse.group/u/FEAnalyst)\ **Post date:** [October 16, 2022, 10:19am UTC](https://prepomax.discourse.group/t/temperature-doesnt-work-with-buckle/455/1 "2022-10-16T10:19:49Z")
Hi, much to my surprise, I’ve noticed that the Defined field → Temperature (`*TEMPERATURE`) cannot be used in the `*BUCKLE` step even though it’s possible in Abaqus. PrePoMax gives the “Job failed - no results exist” error while submitting from the command line results in the following message from CalculiX solver: > \*ERROR reading \*TEMPERATURE: temperature loading is not allowed in a linear buckling step; perform a static nonlinear calculation instead The error occurs also when the temperature field is deactivated and only `*TEMPERATURE, OP=NEW` is left in the input file. Due to this limitation of CalculiX, I’d like to suggest removing the possibility to define the temperature field for linear buckling analysis and leaving it only for the static step. ---
**Author:** ![Matej](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@Matej](https://prepomax.discourse.group/u/Matej)\ **Post date:** [October 16, 2022, 1:52pm UTC](https://prepomax.discourse.group/t/temperature-doesnt-work-with-buckle/455/2 "2022-10-16T13:52:23Z")
I have disabled the creation of the temperature fields inside the Buckle step. ---
**Author:** ![Matej](https://avatars.discourse-cdn.com/v4/letter/m/a698b9/32.png) [@Matej](https://prepomax.discourse.group/u/Matej)\ **Post date:** [October 16, 2022, 1:52pm UTC](https://prepomax.discourse.group/t/temperature-doesnt-work-with-buckle/455/3 "2022-10-16T13:52:31Z")