The Raiders and Las Vegas announced months ago that the deal to move the Raiders to my hometown of Las Vegas has been finalized. I didn't write about it at the time because there was still a lot of unknowns. As you all may know, I was not initially receptive to the stadium financing plan. The city of Las Vegas went all in and basically gave the Raiders almost everything they asked for. Las Vegas would raise room taxes on tourists in order to pay for the largest portion of the stadium's construction budget. The Raiders looked like they'd be given numerous tax breaks (including tax-free bonds and property tax exemptions). It looked like the Raiders would even get out of having to pay rent for the stadium (which is supposed to be owned by the Las Vegas Stadium Authority, rather than by the Raiders themselves).

Being a UNLV alumni and a UNLV football season ticket-holder, a lot of my early frustrations were with the Raiders' (and the city's) insulting treatment of UNLV's football team. UNLV had been unsuccessfully lobbying for years with the city of Las Vegas to get funding for a new stadium. That UNLV stadium came close to happening. It was hoped that having a shiny new stadium on or near campus would increase attendance, allow UNLV to recruit higher-caliber ball-players, and maybe even potentially attract an NFL team (like the Raiders, Rams, or Chargers) to relocate to Las Vegas. Those plans fell apart, as the city simply couldn't afford such a project, and the Rebels didn't help matters by continuing to disappoint with two-win seasons. Then the Raiders come along, and not only does the city give them virtually everything they ask for, but the Raiders also tried to screw UNLV out of even being able to realistically use the stadium that was being mostly paid for by public funds.

UNLV had been unsuccessfully lobbying for a new stadium [LEFT] for years,
then the Raiders [RIGHT] show up and the city bends over backwards to accommodate them.

The Raiders initially wanted UNLV to pay a $250,000 stadium rental fee per game! This is despite the fact that the largest chunk of funding was supposed to come from public money generated by Las Vegas taxes, and that the stadium was to be technically owned by the LV Stadium Authority. If this were a public stadium (as proponents often insisted it would be), then the local public university shouldn't be paying a private corporation for use of the property. In addition to wanting money from UNLV, the Raiders also didn't want to allow UNLV to paint the turf or have any permanent UNLV branding in the stadium. Essentially, the Raiders didn't want to share this stadium that was being paid for with public funds.

A final concern was with parking and traffic infrastructure. Las Vegas' highways are already over-taxed (and perpetually being torn apart and expanded), and the stadium was supposed to be built in an area of town that already suffers from a lot of congestion. ...

It's tax season, which is not something that I ever write about on this blog. But this year, I had a very irregular experience. It wasn't with my taxes; rather, it was with my dad's attempts to use this year's TurboTax software. He'd been using TurboTax for years with no problem, but this year, the program wouldn't install. He's not exactly tech-savvy, so he had to call me to help him troubleshoot.

TurboTax fails to install due to some unspecified issue with the .NET Framework.

Upon attempting to install the program, he gets a very un-descriptive error message that simply states there was a problem installing TurboTax. Then a dialogue pops up stating that TurboTax is attempting to fix the problem by checking the file system, registry, and .Net framework. It's the .Net Framework step where TurboTax fails with yet another very un-specific error.

We tried updating Windows, disabling anti-virus software, and even opened up the registry to make sure that all the requisite versions of .Net Framework were installed. No luck.

Unable to resolve the problem itself, TurboTax referred us to a troubleshooting web page.

TurboTax referred us to this troubleshooting page, which includes instructions for downloading and running various .Net Framework repair tools and other system file integrity tools. In my dad's case, none of this stuff worked. As a last resort, the troubleshooting guide referred me to a blog post by Microsoft developer Aaron Stebner, who wrote about a .Net Framework cleanup tool that could potentially be used to resolve the issue...

Back in April, I expressed my dissapproval of the Raiders plan to relocate to Las Vegas. At the time, my primary objection was to the idea of building an NFL-size stadium adjacent to UNLV's campus. But as time has moved on, the plans have shifted, and the city has come up with new location proposals for the $1.9 billion stadium, as well as new financing plans. Last week, the Nevada State Legislature, on the order of Governor Brian Sandovall, convened a special session to vote on the proposed stadium financing plan. The successful vote was a win for the Raiders' plan to relocate, but was a major loss for the city of Las Vegas and state of Nevada.

The finance plan requires the city of Las Vegas to raise $750 million in funds from a hike in room taxes for its hotels. This leaves taxpayers supposedly off the hook by passing the bill onto tourists. Critics have complained that this takes money away from Las Vegas schools and other public infrastructure and services, but this criticism is a bit of a red herring, as there were no plans to collect such revenues and spend them on schools or other services to begin with. Critics are valid in pointing out, however, that this does take that money away from potentially being collected for the purposes of funding education or services in the future.

The city, tourists, and UNLV all get screwed

I would be fine with this $750 million price tag if the plan guaranteed some degree of revenue or profit-sharing for the city of Las Vegas. It would be an up-front investment with the potential of paying for itself over the long-term. No such fortune for us Vegas residents. This is a bum deal for the city of Las Vegas, however, as the plan does not allow for any revenue or profit-sharing from the proceeds that the stadium may gain. So public money is being spent on the project, but no money is going back to the public. Sheldon Adelson and Mark Davis are both billionaires. If they really wanted the Raiders to move to Las Vegas, they can afford to build their own damn stadium.

Mark Davis and Sheldon Adelson are both billionaires. They can afford to build their own damn stadium.

What really sours this deal though is that it also presents some other "screw you"-s to the city of Las Vegas. The plan to build a new stadium started out as a plan to build a new stadium for UNLV's football program. But UNLV gets screwed by this deal, as they will actually have to pay approximately $250,000 per game to the stadium's owners in order to play their home games there! They'd have to pay $250,000 per game to "rent" this facility! "Public stadium", my ass! If Las Vegas is raising tax money to pay for this stadium (and we're paying for almost half of the entire bill), then it should belong to the City of Las Vegas or Clark County. If it belonged to Las Vegas, then our public university (UNLV) should be able to use the facility, and should get revenue from ticket sales. Not so, apparently. Make no mistake, this is not Las Vegas' stadium; this is Mark Davis and Sheldon Adelson's stadium.

We don't get the stadium; we only get the debt. NFL teams have a long, sad history of screwing cities with stadium deals...

So right off the bat, Cities XXL is not substantially different from its predecessor (Cities XL). In my time with the game so far, I've only encountered two new features. Everything else, right down to the buildings available and the game interface, are unchanged. XXL hardly deserves to be called a sequel or sold as a new game. It's a content patch, and not even a very good one.

But on the upside, since I never got around to reviewing the original Cities XL, I can just roll them both into one review!

This review will cover both Cities XL, and Cities XXL because they're practically the same game.

When I first started playing Cities XL a few years ago, I was really impressed with it. I hadn't really played any modern city-builder games since SimCity 4, and so the jump to 3-D graphics, the ability to draw curved roads, and the sheer size of the maps was enough to win me over initially. But as I've played the game more, it's limitations and weaknesses have become much more apparent and hard to ignore. This is especially true in the game's interface and controls, which are very rough and full of nagging annoyances. When compared to the much smoother and organic controls of games like Tropico 5, the modern [disastrous] SimCity reboot, and even older games like Caesar IV, Cities XL really starts to look bad.

The biggest deterrent to enjoying Cities XL is its UI and controls. There's nothing that really single-handedly breaks the game, but there's a cacaphony of small, nagging problems that gradually wear down your resolve to play the game. The first thing that you'll notice is the ugly and disorganized interface. There are buttons and widgets floating all over the screen: build icons, overlay toggles, camera control widgets, zoning sub-controls, and so on. You can customize some of the UI elements by dragging them to different places on the screen, but there is no arrangement that really feels comfortable.

Charts, graphs, and table widgets are also ugly and difficult to read or understand, so I rarely use them. There's a lot of depth of information in these widgets, but they are just so poorly designed as to be nearly un-useable. And while some info-widgets show a great degree of granularity and precision, others are oddly abstracted. For example, shops and industrial buildings say that they require a "medium" number of workers of various classes, but they don't specify exactly how many employees they require. I assume that "low", "medium", and "high" correspond to the respective sizes of the residential zones, but I don't know for sure.

This office building had to close before I found out why it was unsatisfied.

Feedback in general is one of the game's weaknesses. The "satisfaction" level of buildings are all shown as colored circles rather than actual numbers. Those colored circles that indicate the satisfaction level of a building can be highlighted to show the percentage of satisfaction, but it won't necessarily give any indicators as to what is influencing that percentage...