Menu
▾
▴
#983 An invalid argument was encountered.,rarely when edit events
This has happened to me in 0.99.42, as well as the previous stable version.
Rarely when I edit a condition, by double clicking on it (I mean such as, 'Player 1 "Move Left" is down'), an error will pop up: "An invalid argument was encountered."
Then, some UI elements will not be drawn. The icons in the menus will not be drawn, and text fields in the condition editor window will usually be blank unless I type, then the newly entered letters show up very briefly if I remember right. Object icons will not be drawn in the object selector in the condition edit window (the window for choosing what object to collide with, that sort of thing, not the window for choosing properties or variables to add to expressions).
When it happens in 0.99.42, if I mouse over the condition-edit window buttons such as "Finish" or "Back" the error will pop up again, but just once, and then the button's text will disappear and then it won't trigger the error message again. I don't remember if that happened in the previous version.
It only seems to be cosmetic. I can still click finish or cancel in the condition editing window and save my project.
I do not know if there is something specific that triggers it. I can edit the very same events at other times and won't have the problem. I can close Construct, re-open the project, and edit the very same events without the error.
It seems easier to trigger in my project with many events, as compared to a new cap. I couldn't get it to happen in a new one, though I may not have tried editing an event enough times.
I triggered it a couple of times while editing one by one my many, many Player key pressed events to fix it saying Player %1, changing it to Player 1 (after upgrading from the last stable version of Construct).
GeForce 8800 GT, drivers version: 186.18
When upgrading Construct, I had let it run the DirectX updater again just in case.
Windows XP SP2
A variant also rarely happens after editing an animation frame and closing the picture editor window.
Some UI elements won't display, such as icons.
If I try to edit an animation (double click an animation to edit it) when that happens, Construct will actually crash, giving the "You should probably report this!" sort of message.
I just don't know, since it is so random, not consistent. I can edit animation frames many times or edit events many times without it happening, then it will without my apparently having done anything different.
Oh yes, on a very rare occasion when this happens, it has also somehow affected my Windows taskbar icons - they won't show in the tray, just filled with white. Ctrl-alt-delete then cancel refreshes the screen, and they redraw. But it is only Construct that has done that to me. I think it might be just the animation-editing variant that's done that to me.
Still, I wouldn't be surprised if it really is my video card + drivers.
This also happened to me with a GeForce 8500 GT (512MB), NVidia drivers 190.62
I am quite sure that 8800 GT I was using was having texture memory problems of some sort, but I haven't seen any on this card yet..
I seem to get this invalid argument thing every 20-30 minutes or so when working with events, as well. I've sort of grown use to seeing them everyday though.
These bugs are memory leaks. If you open up the task manager, you'll see construct's memory usage continually increase every time you either open the expression editor, the picture editor, or edit the text in an event in the event editor without opening the event by double-clicking it.
For the expressions editor, the frequency which the bug occurs is dependent on how many objects (not sure if they all have to be sprites) are listed in the box with all the icons below the expressions. More objects there, the less times the expression editor needs to be opened before it will crash. To re-create the bug, simply make a new game, insert a sprite, fill it with a color, copy it and paste two or three hundred (or however many construct will let you paste before it slows to a crawl) clones (not instances!), then make a new event checking a pv of one of the sprites, and repeatedly open and close it. Depending on how many sprites you have, it shouldn't be long before construct crashes.
Each time I open and close the picture editor(again, with many, many objects), construct's memory usage launches a few megabytes.
also found another memory leak and a way to tell when construct is going to crash. Simply clicking a sprite once in the layout editor to highlight it, then deselecting it by clicking away from it, the memory usage continually increases as well.
I realized that if I leave the task manager open, I can find out how much memory construct uses before it crashes. Simply leave the task manager hidden in a corner with only the memory exposed, and if you check it each time you edit something, you'll know when you have to restart construct.