yosh56

All that being said...Obelisk is still gonna shoot aircraft. Technically, according to Renegade's tutorial, the AGTs advantage over the Obelisk is its ability to fire on aircraft... But that went out the window when we got aircraft hastily slapped in with no SAM sites or the like. Aircraft already have enough advantages, and a lack of counters (less so since 5003), so having high tier base defenses kill them really just keeps them on a more level playing field with ground vehicles. On top of that, in most situations on a map like Eyes, you can avoid the Obelisk fairly easily. Walked more than enough Trannies through Nod's front door.

I....have no idea why it happens. Even randomly happens in single-player

You could use the binoculars in vehicles that didnt have weapons, or if you were in the passengers seat.

Rep tool was just not implemented, but code wise it's mostly all there. It's just a repair gun with ammo. If anything I wouldn't mind seeing this added in the base game somehow

Let's rain death, sounds good Lol yes. This actually reminds me of... 'BRING THEM TO THEIR KNEES!' Technical wise, it's going to be quite a work on Dev side though. Each vehicle seat is set to a certain weapon. One will need to script a weapon that detects the pawn's own weapon or make weapons for each pawn's weapons..... or some other tricks that escapes me This isn't difficult at all...hell, I already did it by accident once in the commander mod.

Left my keys in a taxi. gg

I'm locked out, soooo don't expect me. It's all up to Nanas for getting the server up and right

I like how nobody batted an eye at The Yosh buffing the Chinook in 5003.

I feel like the biggest 'issue' with AOW right now is the fact that there is literally no point reward for killing off a building. It's worth 600 total... but on destruction you get nothing, so in reality point whoring is ALWAYS the better option. So, I was thinking that more than likely buildings are going to get some type of point reward in the future, but curious as to how much. Too much might be annoying, but not enough leaves us with what we're at now. I'm thinking 1500 for destruction myself. This would go to the team, not to the individual that destroyed it.

There SHOULD be, however B0ng wont be able to make it... and it depends if I go anywhere or not.

^^ That.. Don't be a Yosh.

I would just download and apply the manual patch. Oddly enough though, you should be fine as is because of the file that errored out. That file will just have to build itself, and may slow down some of your map-loads once or twice. So, you should be fine.

No...don't do that. That will be the fastest way to aggravate me.

Always

Shot in the dark... but I was thinking that we only do spawn points in buildings because they've always been in buildings. What if, for infantry only maps, spawn points weren't actually in the buildings themselves? Say like... there was just a dormant APC or Landed transport prop at the back of the base with PTs, and (maybe( still PTs in buildings. If people didn't spawn right back in buildings, I don't think it would feel so helpless rushing with other infantry, as you wouldn't just be putting your enemy RIGHT BACK IN YOUR FACE. It's already hard enough to not get wtf pwned by people with remote C4 (and a decent ping).

You can't change constant variables dynamically (So they have a default value and that's it). To change things regarding infantry/vehicles/weapon classes in the purchase system, you'll have to extend the purchase system and change default values.

I can tell you your guy's problem on Islands.... That smoke in the faces of your big fat Mammoths =O!

The game depends more on your CPU than GPU honestly

I have been inspired. <3 Also.. no team retention mutator... we ran into some issues with senor RCON

Only thing I can think of that would have changed and possibly messed with anyone in 5003 is the config files. Look in your UDKGame/Config folder and see if there are multiple UDK[Whatever].ini files beneath all of the Default[whatever].ini files. There should be one UDK file for every Default. --- On that same note, the Default resolution changed in 5003, so if it's worth a try, you can look for either UDKSystemSetting.ini (this is the one the game uses), or DefaultSystemSettings(this is just the default one it uses if you haven't ever ran the game). In either of those search for "ResX" and ResY, and set them to your preferred resolution. E.G I run 1920x1080, so it'd be ResX=1920 ResY=1080 - On that same token, you can look into editing both SystemSettings.ini, and RenegadeX.ini to reset all of your graphics settings and see if that's where the error comes from.

Let me know when you're done finalizing.

Sure that's where the log ends? Should be slightly more on that last line before it cuts out. Either way, if that's where it ends, it gets to setting up the map list... so try bypassing that really quick and we can go from there. In the RenegadeX/Binaries/Win32 folder open a command prompt (if you hold shift and click in the window it'll have an option to open a command window there), then run "UDK CnC-Field -log" If it lets the entire map load, then there may be a corrupted Front-end-map package in your maps folder... or something of the like. (Note... you may not be able to get past the countdown if Field does load.... but that's a known issue)

Right click and run the game (not the launcher) as an administrator. If that doesn't work, post the last ~50 lines of your launch.log file from your "Renegade X\UDKGame\Logs". It's kind of difficult to figure out what exactly an issue is if it just miraculously locks up. (It may be Launch_2.log... just choose whichever one was updated most recently)

Navigate to where RenX is installed (Usually "C:\Program Files (x86)\Renegade X"), and copy and paste the Folders from the manual download's folder into the the RenX folder. That simple. If you're on Windows 7/8/10, you should just be able to copy the UDKGame Folder into the main RenX installation directory, and it'll just overwrite the files it needs to.

There's already a topic for feedback on Valley.