Jump to content
SAU Community

Recommended Posts

I STILL can't get C&C3 to work...can't even get passed the initial installation process...

Error1316. A network error occured while attempting to read from the file E:\cnc3std.msi

i returned it and got another copy but still the same shit...so annoyed

i hope i don't have any problems with Red Alert, though...i agree with you on RA2...awesome and fun game!

Link to comment
https://www.sau.com.au/forums/topic/232479-cc-red-alert-3/#findComment-4083634
Share on other sites

I have a beta key for RA3 however I need to download it and so far havn't done so..... Seeing as it releases in a month I may not bother and just get the full game.

For it to succeed in my book it just needs to be non-buggy. C&C3 and kane's wrath expansion was so buggy to the point I raged and uninstalled it a month ago to never play it again. With EA taking over all the companies that make decent games and then monopolising and marketing the new games it makes for alot of mediocrity..... I hope RA3 is something that EA does a good job with :dry:

Link to comment
https://www.sau.com.au/forums/topic/232479-cc-red-alert-3/#findComment-4083782
Share on other sites

nah mate it didn't have any viruses on it...... but then again I did buy it when I was in taipei and all the instructions are in chinese :(

but yeah it had issues especially on kane's wrath whereby if you ran a different resolution from what you were running in windows it would crash randomly - this was a common problem that could only be fixed by changing in game resolution to your windows one (only reason I was running a lower ingame resolution was to improve frames per second as it was a big slow at times).

Another issue I had was if I ran a skirmish game with any more than 3 computer AI opponents it would crash before starting. Alot of other people on gaming forums had the same problems as me and EA did nothing about it.

My computer is about 3 years old but with upgrades etc. it does sit above the minimum specifications by a fair bit so theoretically it shouldn't have any issues. That said the resolution/crashing issue was reported by people with top of the line systems with 8800 gfx cards......

Anyhoo I hope RA3 is better :D

RA2 wasn't that bad tbh

Link to comment
https://www.sau.com.au/forums/topic/232479-cc-red-alert-3/#findComment-4085436
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • For once a good news  It needed to be adjusted by that one nut and it is ok  At least something was easy But thank you very much for help. But a small issue is now(gearbox) that when the car is stationary you can hear "clinking" from gearbox so some of the bearing is 100% not that happy... It goes away once you push clutch so it is 100% gearbox. Just if you know...what that bearing could be? It sounding like "spun bearing" but it is louder.
    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
×
×
  • Create New...