I've had no issue with this font crashing Flash CS6, whether multiline or single, selecting various parts of text, multiple TextFields, antialias for reading or device, embedded or not. But I am on Windows (not on a Mac).
Have you tried all font-families under Oswald? (Light, Regular, Bold)
Oddly I don't get those, although 3 were installed. Here's a video of me using it (as you can see the family is grayed):
You can see that book is initially selected however which tells me it's reading the varients. I'll try a system reboot and see if anything changes, I'm due anyhow..
It's also possible it is related to the Suitcase Fusion 5 software (it might of modified other system settings during installation, other than running FMCore.exe at the start).
I'll try uninstalling it later, but it would be a shame if I can't even use it. This was the whole point that I got it in the first place. Anyways, will investigate further later.
Ah yes, I had the same issue initially (regarding the "Book" family locked and selected).
For that, I uninstalled the "Book" version, restarted Flash CS6 and it allowed me at least to change between "Light" and "Bold". No system restart was required (then again, I managed it with Suitcase Fusion 5, but I doubt you would have to restart everything).
See if that let's you pick between the two.
And also, I noticed in your video that you resized by typing in the values mostly. Can you try by dragging and sliding the values instead? That's when the BSOD seems to happen the most. Typing the size seems to be the only quick fix at the moment, but I would prefer to drag-slide the value when eyeballing text to fit in the context needed.
Thanks again for taking time to check this bug.
Sure, no difference here with sliding or typing. After reboot (or Flash restart) nothing changed. I installed them one by one and Windows prompted me if I wanted to reinstall over the existing font. I said yes. Suddenly all 3 appeared just fine.
They work, embed or device, except bold on device seems to get cut off half way down as if the line height is messed up. Set to antialias for readability solves that though:
There's definitely something odd about it in general, or Flash's handling of it. You can see I can barely even select the text sometimes, I need to draw a box around them. The characters aren't being clicked.
Overall no crashing so I can't say it's Flash CS6 or the font at this point unless as you mentioned, suitcase altered the fonts on import. The bare fonts themselves with no font management software work just fine for me.
Just about to do a quick test now that I uninstalled Suitcase Fusion.
Back from a restart after YET again, another crash (after the Suitcase uninstall).
Though I was able to work with the font in a new document, I wasn't able in the one particular ad I'm working on. I guess I would have to share that as well.
Here is the FLA in question (this isn't the only one that causes the BSOD though):
- Double-click to open the CLIP_MC symbol in place.
- Press SHIFT+> to navigate to the last frame of the ad.
- Double-click the symbol inside the FINAL_TEXT layer (symbol name = "FRAME_04_TEXT").
- Finally, double-click the text "WE'VE GOT ALL THE INSIDER" on the right hand side to begin editing it.
At this point, it crashes immediately when I try to double-click that field. It's getting nuts!
NOTE: In case this detail helps, I am using preview mode "Anti-Aliased Text". Doubt that's the reason it crashes though.
1 person found this helpful
Although I didn't have one of your other fonts, Oswald is working ok:
Everyone other than myself at my agency has a Mac (OSX of various large cat versions). They all have dual quad xeon stations with 32GB+ ram and discreet video cards. The systems are beefy, but even fully booted to Windows, they run absolutely terrible. This could just be a situation where you should try editing in OSX. I've seen a Mac running Windows do countless odd things, especially when it came to utilizing sound or GPU hardware. As much as they'd like it to be, that isn't really Windows running on all cylinders. It's just begging for random issues.
Thanks for checking into it. The Mac Pro I'm using works smoothly on Windows 7 (perhaps because I turned it down to Win98 style?), but anyways I think I may have found the issue.
I'm going to try uninstalling another program that might of been the culprit to other display issues I've been experiencing (such as Chrome displaying black regions where videos / youtube clips would normally show up). Avatron - Air Display Support might be the problem I'm having.
Gotta uninstall, restart and try again. Will keep you posted.
1 person found this helpful
Page faults are typically issues writing to the page file (c:\pagefile.sys). Paging happens for a variety of reasons. One of which is when you run out of physical RAM. Once you're out of RAM it starts to use the system page file as RAM (very slow and you can head your HD crunching away). Something is having a problem using that file. Check you're not out of file space and although I don't recommend changing Window's default settings, you might want to manually increase the size of the file.
To do that, click the Start button, right-click on Computer on the right and select 'properties'. You start in the 'Advanced' tab (or select it), then under the top 'Performance' option click the 'Settings' button. Choose the middle 'Advanced' tab. On the bottom is the system pagefile (Virtual memory). Set to 16GB typically by default. Click the 'Change' button. At the top by default the OS has 'Automatically manage paging file size for all drives'. Uncheck the option. Select a drive in the list you know you have a lot of FREE space on (50GB+ bare minimum). In the middle, select the "Custom size" radio option. In the initial size and max size to 24576. Click the 'Set' button. Click 'Ok' at the bottom and it will force you to reboot.
Now you have 24GB instead of 16GB for your pagefile. If you somehow run out of space with that, you're definitely using wayyyy too many applications at the same time and need to buy more RAM.
If I do go that route, should I assign my pagefile on a Hard-Disk drive, or an SSD drive? My guess is Hard-Drive to avoid too many frequent read/write operations (on the SSD) by the OS, correct?
SSD will significantly increase the speed and these days the old "finite r/w SSD" problems are essentially eliminated, so I'd say either is fine if you have a modern SSD. The pagefile isn't used terribly much (mostly background/idle usage) if you have plenty of RAM. In this case you should be telling bootcamp to give you adequate extra HD space (at least 50GB wiggle room as mentioned) and should have at least 4GB physical RAM. I don't know of many development rigs under 16GB with RAM so cheap but, you're on a Mac .
That said, I'm coming from a purely Windows/Intel PC setup with proper modern drivers.
I'd choose the SSD, if it has the space and access and it appears to work fine with your drivers. If things start crashing often, change back to the HD.
Oddly enough, I miraculously stumbled upon this security bulletin:
The patch I downloaded specifically for my system was this one:
Windows 7 for x64-based Systems Service Pack 1
I'm not exactly sure which files it replaces, but seems like it deals with potential vulnerabilities in OpenType fonts, such as Oswald. Not saying it was corrupted or viral, but could of simply been intended for Mac perhaps, and not fully compatible with Windows... maybe... I'm guessing.
Anyways, so glad it's over! Phew! Lost so many hours looking for a solution. And uninstalled so many programs that had nothing to do with it... argh!!
Good luck to anyone else with the same issue!
1 person found this helpful
Oswald works fine for me and I have every patch. Are you saying your issue is fixed now? It doesn't suggest that when you mention the font might only be for Mac (it works fine for me as you can see in all the videos). Definitely keep windows up to date (allow windows to update itself automatically) and things like this won't happen. That's a little but important thing that can slip by a Mac-heavy user. Microsoft must ask you to do everything whereas Apple (legally) is able to do a lot more for you automatically.
If you're all set please mark any helpful/correct so we can filter unanswered questions. Good luck!