wlape3

I had the same error appear on my laptop which still runs WinXP. Reloading the game solved the issue.

This feature does not always work as expected. For instance, when plotting an artillery unit, it will fire on any tile which is a valid target rather than simply traveling there. :eek:

I measured the execution time of the same turn with the processor affinity set to a specific CPU and when it was not assigned to a specific CPU. The times were faster when the affinity was set but not enough to say it really made a difference. Total time running normally was about 5 minutes. Running with a specific affinity was about 20 seconds less. Only a 5-7% improvement which could be explained by the differences in random events and AI actions between each execution sequence. Oh well. YMMV...

Yes. I tried it this morning and the game engine certainly feels faster but I haven't timed it yet.

Here is something to try. Next time you play, start breakthrough and then start up the task manager. Then click on the "Processes" tab, click on the button on the lower left labelled "Show processes from all users" (this elevates task manager to Admin status) and then right click on the process called "SC-WWI Breakthrough.exe". Click on "Set Affinity" and assign it to one of your idle processors. This will allow the program to execute faster since it should be the only task running on that CPU. You can use this program: http://www.mediafire.com/?b3io2coj3h8hc1n to set the affinity for the game engine permanently. You can also go into your bios and set which CPUs your OS will use by default. Set up all but one for the OS and you should then be able make the deselected one your gaming CPU by setting the affinity for your game executables to this CPU.

I use an AMD FX8150 with an SSD drive and a HD6950 GPU. Total RAM is 24 GB running under Win 7 Ultimate 64 bit. The GPU and RAM are overkill but the SSD helps the game load much faster. My recommendation would be to get a 4 core Intel chip like an I5 sandy bridge and run it under Win XP 64 bit. Win XP executes it faster than Win 7 and the 64 bit OS will allow you to get more than 4 GB of memory in use. The game seems to execute mostly in memory and I would think a fast CPU and reasonably fast memory would be best. The AMD chips are cheaper in the US and a good value but the Intel chips do run the code better, probably due to the fact most compilers are optimized for Intel CPUs.

By the way, for those of you just getting into modding, using MS Paint included in all versions of Windows you can easily resize any custom bitmaps you may have. Thanks again Hubert...once again you guys set the gold standard for support.

The scenario is a custom one which was built by importing the attributes through the editor and all of the associated scripts execute properly. One thing I didn't do was to update the bitmaps in the custom folder. As you say, some of the bitmaps have changed quite a bit and I found that replacing one of these, the symbol_sprites.bmp, seems to have solved all of my problems. However, it's possible I could have issues with one of the others as well. If this is the case I'll report back here so other modders won't have the same issues. Thanks for the quick reply Hubert and I do apologize if the bitmap differences were spelled out in the literature since I just assumed only the script parameters had changed. Will

I do agree with you that large ships are too easy to sink but WWI may not be the best time period to state your case. In those days, the concept of "Fleet In Being" was more important than risking the fleet to damage your enemy's fleet. The relative lack of significant damage to the Imperial German fleet at Jutland may have had more to do with the fact the German ships were well built and the crews well trained. They were able to avoid being broadsided numerous times despite being outmaneuvered at key junctures.

Having a lot of problems running a WWII scenario under the upgraded Breakthrough engine. The game keeps crashing when units are moved, placed automatically or upgraded. Reducing the graphics to minimal effects seems to lengthen the time between crashes but not eliminate them. Most of the fatal errors are segmentation violations. Here is one example: FAILED(draw_unit_tertiary_level_to_buffer): Segmentation Violation. This does not seem to happen on my laptop which runs WinXP 32 on intel graphics but happens routinely on my game PC running Win 7 64 with a Radeon 6950 and 24 GB of DDR3. The Great War engine runs this same scenario on both machines with no issues and no hardware changes have been made. The scenario was rebuilt in the Breakthrough engine using normal importation techniques. All the scripts were rewritten with the new parameters and successfully compiled. Any thoughts? My gaming PC has a lot more horsepower than my laptop so I'd prefer to run the game there. Will

Edited previous message to include text of error. dderr_invalidrect Got it to go away for now by reducing the visual options (highlights, scrolling without text, etc)

Has anyone seen this before? dderr_invalidrect Any thoughts on how to correct this?:confused: The error is appearing in a custom WWII scenario for Breakthrough. Will

My understanding is the former. You will need to have a copy of the original game to use the expansion. Usually, there is a bundled price where you can buy the game plus the expansion for a savings in shipping or a small discount.

Perhaps that is for a version other than the US version? In this electronic age I would think you could buy any version as a download only. Another possibility is the VAT is huge.:eek:

I think there is already a return to hexes planned. Multi-threading still seems to be "a bridge too far" though.

As long as it is enabled in the options screen you can undo any move which has not been "finalized" by clicking on the undo button in the upper right hand corner of the screen. Moves are finalized when you either: 1 click on another unit/map location 2 right click on the unit you just moved or in another location 3 encounter a previously hidden unit while using fog of war.

Did you go back into the dialog box to make sure they were disabled? Another possibility is that there are multiple scripts controlling that event and you only disabled one of them.

Check your PMs.

Wouldn't the screen be too small on an ipad? I think my 22 inch screen is about the minimum size to really appreciate SC2.

Yes, there are size limitations to what can be displayed. Try reducing a few and see if the crashes associated with those events go away.

Once upon a time I downloaded everything on that site for SC1 and SC2. If you know a text string I can use to search for it I may still have it since I never throw anything out gamewise.

I totally agree. This has been my experience too. The editor rarely, if ever, freezes on me. Sometimes it just takes a very loooooong time. When it does crash it either pops you right back to windows or kicks out an error message. One thing you should be wary of though. The editor and the game itself don't always like being minimized.:eek:

Probably. Starting from a clean copy and then making incremental changes is the surest way to troubleshoot the scripts.:cool: When the scripts are error checked from inside the editor it can be a little frustrating as it will stop on the first error and you may have to go through many cycles before finding the problem if you've made too many changes at one time. I like Notepad++ because it allows me to search and replace across multiple files. This is great when updating minor country names or conditions centering around a set geographic location or time.

Is there a highlighter file you use/recommend for SC2? Just wondering if conTEXT has any functionality beyond Notepad++.

Stalin was an opportunist so the scripts model this rather well. You can always try diplomacy to slow Soviet mobilization but I think the mobilization modifiers are pretty hefty once you lauch Seelowe. You should also have the USA climbing up your back soon as well.