Armies Of Exigo Widescreen Fix at Software Informer. Flawless Widescreen 1.0.15 Free. It helps you adjust the very high resolution displayed on ultra wide monitors. Flawless Widescreen is a tool. Armies 1.1.864.2248. Raspina Studio 173 Commercial. Minimum Recommended Operating system (OS) XP, ME, 2000, 98 SE XP, ME, 2000, 98 SE Processor (CPU) 1.5 GHz Intel Pentium processor or AMD Athlon processor equivalent 2.8 GHz Intel Pentium processor or AMD Athlon processor equivalent System memory (RAM) 384 MB (512 MB needed for 3 or more players) 768 MB Hard disk drive (HDD) 1.5 GB 1.5 GB Video card (GPU) Nvidia GeForce3 or greater ATI Radeon 8500 or greater 64 MB or more of VRAM Nvidia GeForce4 or greater ATI Radeon 9600 or greater 128 MB or more of VRAM Notes. Making maps and messing with world editor for a long time, ive gathered things that i think should or could be edited and changed. Xforce keygen 64 bit 2017 autocad. - Being able too color code triggers for better organization. - Being able to transfer triggers to other maps so you don't have to redo variables and everything. - Being able to change cliff types too whatever you would like instead of making a whole new map. - Being able to change terrain tilesets without having the red box making it so you cant change it, you should be able to change which ever tileset and cliff type whenever. - Being able to import models/skins/icons without any stress, without having too edit each one and add a special code towards it, just import the resource and that's it. - Being able to organize doodads in folders and maybe color code them to find better. For example, you gather all the doodads you would use in your map and put them all in on folder so they are easily found and can be used. - Being able to add more doodads than the limit that it has. ![]() - Being able to, when making a new map change tilesets and rearrange them with ones you would want or don't want in your map. There is alot more but this is just some stuff ive collected. Im sure some of these will or will not happen just wanted to throw it out there. True Hashtables would be nice. ![]() Eg the following could in rare cases be true and cause heisenbugs: StringHash(a) == StringHash(b) && StringHash(a)!= StringHash(b) to fix it it would be nice to have native hashtables that took actual native types as keys and ensured correct operation on hash collisions. Also the silly limit on the number of hashtables. Why does it exist??, just get rid of that nonsense. And the 2 key api for hashtables. I know it mimics gamecache. But still nuke it ( deprecate) and get sth actually reasonable. EDIT: i meant this: StringHash(a) == StringHash(b) && a!= b.
0 Comments
Leave a Reply. |