AwesomeMod Bug Report Thread

<< < (119/334) > >>

RebelRed:
Playing the goth family getting random CTD after 1, 1 1/2  sim day of play.  Having a destination party, it either crashes before the party or after.  Not sure if this is the cause, but it's done it twice now.  Vanilla game with AM 3/9 patched to 1.32 have all ep. 

Shamino:
Quote from: J. M. Pescado on 2012 March 14, 18:27:29

Now, by a "Stage", you mean that this is a community lot, right?


Yes, when using the sim-option to build a custom set for the stage right before the performance begins (where stage props are the only items available).

In regular buy-mode I get charged normally.

Batman:
Quote from: Shamino on 2012 March 15, 16:38:44

Quote from: J. M. Pescado on 2012 March 14, 18:27:29

Now, by a "Stage", you mean that this is a community lot, right?


Yes, when using the sim-option to build a custom set for the stage right before the performance begins (where stage props are the only items available).

In regular buy-mode I get charged normally.


I also have been experiencing this.

Thanks again pescado for your quick updates :)

Noromarc:
Game is patched to 1.32, all expansions added, with Awesomemod dated March 9 local time. Game allows portable instruments on a community lot stage to be dragged in live mode, causing immediate "TS3 has stopped working" crash and subsequent shutdown. Removing Awesomemod allows normal game interactions, where the mouse cursor is an arrow with a sprocket and these same portable instruments cannot be dragged.

Edit to add further observations. The game crashes whenever I drag an object while the cursor bears an arrow and a forbidden symbol. Sometimes the cursor remains as "go here", the arrow plus feet soles, but game will still crash if any mouse motion is applied while left-clicking.

Edit to share more information and a question. Whatever object is left-clicked and then dragged while playing in live mode on a community lot causes immediate game shutdown. It can be a decorative object, furniture or even drinks. Now using patch 1.33 with Awesomemod dated March 17 local time. Removing every custom content file except for Awesomemod (with and without aweconf) still causes the issue, while removing it restores expected behaviour. Am I the only one experiencing this?

WyattMatthews:
I'm just inquiring as to when you will be bringing out the new version of AwesomeMod that is compatible with the newest update?

Or will you not be doing that?

Please let me know.

Regards,
           Wyatt.

Navigation

[0] Message Index

[#] Next page

[*] Previous page