Edit Squadrons crash and map size

Matrix Games Forums

Forums Register Login Photo Gallery Member List Search Calendars FAQ

My Profile Inbox Address Book My Subscription My Forums Log Out

Edit Squadrons crash and map size

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [Current Games From Matrix.] >> [World War II] >> Carriers At War >> Carriers at War Support >> Edit Squadrons crash and map size

Page: [1]

Message

<< Older Topic Newer Topic >>

Edit Squadrons crash and map size - 2/12/2008 10:51:46 PM

Unhappy

Posts: 124
Joined: 6/9/2007
Status: offline

Hi. Sorry for asking so many questions.

First, attempting to create a new scenario (from scratch) and get a crash to desktop everytime I hit the "Edit Squadrons" button in the editor - so I can not get in to the Edit Squadrons screen at all. This is a new issue for me (since 1.02 patch).

Second, don't suppose there is anyway to unlock the standard map size of 84x72 hexes? I would love to be able to try a huge map of 210x180 but would very happily settle for 105x90.

Post #: 1

RE: Edit Squadrons crash and map size - 3/12/2008 11:36:11 AM

alexs

Posts: 417
Joined: 8/27/2003
From: Sydney
Status: offline

Hi Unhappy,
Late reply but
1. Fixed in the last patch.

2. We are looking at that for the future, though we havent come up with an elegant solution to handling the arbitrary aspect ratios that will crop up.

_____________________________

AlexS
SSG
Support@ssg.com.au

(in reply to Unhappy)

Post #: 2

RE: Edit Squadrons crash and map size - 12/21/2020 8:16:06 PM

tbates774455

Posts: 1
Joined: 4/23/2020
Status: offline

Hello,
Hopefully, I am putting this in the right place.
I am also having this problem. When I tried to create a new
scenario and I push the "Edit Squadrons" button it crash to
desktop. I reinstall the game along with the beta upgrade, but
it still do the same thing. Any help will be welcome.
Thank you in advance.

< Message edited by tbates774455 -- 12/22/2020 1:06:01 AM >

(in reply to alexs)

Post #: 3