Jump to content

Einstein

Staff Moderator
  • Content Count

    2,916
  • Joined

  • Last visited

  • Days Won

    68

Einstein last won the day on November 6

Einstein had the most liked content!

Community Reputation

745 Excellent

2 Followers

About Einstein

  • Rank
    Keeper of the Beta
  • Birthday 06/03/1993

Profile Information

  • Ingame Username
    Einstein
  • Gender
    Male
  • Location
    Mississippi, USA
  • Icon
    none

Contact Methods

  • Steam
    einstein910

Recent Profile Visitors

23,831 profile views
  1. Playable, yes. But there were several issues that were caused due to various changes and fixes in the newer engine, and it could not be released in that state. If you want to see what I'm talking about, install stock Beta, and apply the latest scripts update from the TT website. Thats exactly where I began. Purchase terminals were broken, helicopter cinematic scripts, shaders, screenshots, mechanic and medic healing balance, fog on some maps, function keys, ID collisions on some maps, menu element colors, and a laundry list of other small things I dont remember. Several issues were the product of hacky stuff that was done in the engine back then, and had to be undone in order to work now in the "standard" way. No more special game-specific hacky stuff - we're using the same TT 4.6 engine that Renegade uses now. Just had to make the game's configuration understand that 😉
  2. It seems that I overlooked this question, my apologies. The older versions of "renegade alert" suffer even worse than stock beta does on a modern PC, but indeed the same treatment renders them playable as well. In the same way that 1.2 Beta has been updated, I also plan to release version 9935, which was the final "Alpha" release. For versions older than 9935, I have built a "combination" version that doesnt really have a name yet... 9925x? Simply "Alpha"..? Anyway, pre-993, the versions were all very closely related, and thus compatible with each other moreso than other versions (like Beta -> Delta). Unless someone digs up more, there were/are less than 10 public maps up until 993. So instead of updating 5 old versions of the game with 1-6 maps each, I chose to go a different direction and build this "combo" version from 9925, as it can use maps from all previous versions. With some work, it might even do it correctly
  3. Well for starters, some buildings got renamed so that breaks stuff right off the bat. Old maps call for scripts that dont exist in Delta, etc. It would be out of place both visually and under the hood, and yeah a big timesink to even begin to fix it.
  4. That would have been sometime in alpha (9935 or earlier) if APB ever came with Comrade. Im not sure on that one, it could be a version that I'm missing. I remember that software but dont remember what I played that used it.
  5. Possible - yes. But more trouble than it is worth really. What would be the gain? Sprinting??? Pasting a 12+ year old map into the current version of APB would be very out of place, and again, difficult to do. And I can guarantee 100% before he even sees this, Pushwall will say no Keeping old maps alive is one purpose of the Beta revamp. Same for the 9935 revamp, and others coming. Snapshots of a period of time, made playable with QoL updates and nothing more. Pasting the old maps in their virgin state into a new game would undermine and invalidate that concept entirely.
  6. Was there even a time signature at the end? It feels all muddled, difficult to define. Definitely a cool effect, take that as a compliment and not a nitpick haha. I wish I had time/talent to make cool music like that. Keep it up!
  7. Time will tell......sooner or later.....time will tell.....
  8. More maps indeed! And hopefully a few more to come in the future if they can be fixed. So, waaaay back somewhere in alpha, AircraftKiller added several unused assets for things that were planned to be introduced in the future. They were just hanging out in always.dat and went unused for years, along with tons and tons of assets that had been replaced from previous versions, but were never removed, and even pieces of stock Renegade that never got removed. With the help of some fancy new tools we have now, I was able to isolate these unused bits and remove them, reducing the size by quite a chunk. Also the removal of the nostalgic but unfortunately broken and unusable old launcher of that era, and some scripts 3.4.4 and APB custom pieces that were still in play back then helped to reduce the size and file count, as shown in the screenshots. The folder structure of modern W3D games is far simpler than it was back then.
  9. One of my lab assistants has made an observation that we felt was worth sharing with you... Back in 2007, this is how APB Beta 1.2.0 appeared: And now: Hmmmm... Differences. Seemingly very minor differences, yes. But significant differences indeed! But what ever could this mean? See you soon comrade....
  10. I was not present obviously, but from the exchange I see here, @Kickmofo you have handled this appropriately and with accordance to our rules, the upholding of which you are also bound. People often do not realize the other side of rules is that those with responsibility have an obligation to carry out their duties, even when it may be unpleasant. I'd like to address something else though. @WNxHeadShot One more statement like this will result in action from far above Kickmofo. We don't do threats here, and you'd do well to not forget that. I really don't care if you hate the guy, or me for that matter. If you would like to continue using any of our services, then you'll not make any more threats more serious than "hey Ima nuke ur base d00d". Consider this a formal warning. Now you bois go play and have fun and stuff
  11. So about 6 months ago, I played with Sole Survivor a bit, and actually got it to run standalone (without renegade) and with the latest 4.6 scripts. But it had issues. It is such a custom piece of moddery.... SomeRhino (its creator) may be the only guy who could fix it properly.
  12. What a coinkydink, I'm kinda back now too
  13. Update! A much-needed scripts feature was added today. Developers using the latest 4.6 update can now globally enable or disable the VIS (visual culling) system permanently. What and why? Well, VIS was used originally as a way to squeeze some performance out of the game by "culling" visible objects once they were a certain distance away. It uses fancy math and requires lots of manual setup on the part of the map maker in order to work correctly. So from then (long long ago....) to now, some changes have been made to this system, as well as the level of meticulousness paid by the map makers to its implementation. So what we get when we dump new engine code in with a 12+ year old version of a W3D game, is some really funky looking stuff. What we call VIS errors or "holes". Things that display incorrectly, and can actually be very distracting or confusing depending on where and when they appear. Ok so why is this important? So with 12+ years of engine improvements in other areas, coupled with the (comparatively) simplistic nature of older games/maps, what we get is the lack of need for a visual culling system. So we turns it off The ability to toggle the system off completely with a setting, INSTEAD of having to import every single map and remove or fix the VIS information is obviously desirable. And it has instant benefits! Compare the screenshots below for a fine example of the weirdness that VIS can cause (first shot), versus just turning it off (second shot). Notice that the FPS is still pegged out even with the system disabled. Performance impact is zero. In other news, development on this has been stalled for a little while now, but hopefully will pick up again in the near future. This is the first notable update in a while, but a very important stepping stone on the road to release. We are so close! Stay tuned and hopefully this thing will be in your hands soon!
×
×
  • Create New...