Did you remember to take out your Draw event ever?
One issue I see with the dragon object draw event is that it seems to be drawing the sprites for all 10 dragons.
So each dragon is drawing 10 sprites, and there are 10 dragons, so that is 100 draw_sprite calls.
Probably not nearly enough to affect the frame rate, but still not something you should be doing
@Mallard8
The code you have in the draw event of your dragon as listed above would be better suited to go in a single controller object.
Yes there is one object but there are 10 instances. As I said in every one of my posts, it doesn't matter how many objects there are, what matters is how many instances there are. Since there are 10 instances, it should have been assigning a unique image_index for each instance of obj_dragon. Unless his draw a event was interfering with it, it would appear to be an issue in studio 2 that suggests instances are all created at the same time when the room is compiled. However, that also runs contrary to instances not existing at the start of a room.
ah, I missed the part about it being dragged to the room ten times. Instances, however, are not all created at the same time "when the room is compiled". This of course makes no sense.
Just to re-confirm what I had discovered previously, I made a test object and in its create event printed out the instance_number() for that object. Then I placed 5 of these objects in the room via the room editor.
The debug output is as follows:
id :100007oTest Count: 5
id :100008oTest Count: 5
id :100009oTest Count: 5
id :100010oTest Count: 5
id :100011oTest Count: 5
I don't know if GMS 1.4 behaviour is different. But in GMS 2, instance_number returns the count for all instances that have been placed in the room editor when called from the Create Event.
Which is different than what I would have expected as I thought the docs said in the order of events that the instances are created one by one and as they are created, their Create Event is executed.
But apparently, all the objects are created first, then their Create Event is performed.
EDIT: Here is the quote from the Event Order section of the docs that made me think it is one by one:
Create Event followed by the Instance Creation Code of each instance - so as each instance is created, it will run first its Create event and then its Instance Creation Code before moving on to the next instance to be created