For the love of JJ2, someone has to finish that boss battle! It's like the most wonderful thing I have ever seen!

Amazing!

Uhh, I think it's Angelscript? I don't know, try making a .j2as file :\

No option for setting FPS limit? Guess JJ2 is toast since I'm going for Windows 10.

This one works, thank you very much!

By the way, did you do anything in particular to improve player movement server-side? There was this nocap-bug which occurred when players were attempting to capture a flag with vertical movement involved, but failed due to them leaving the base too fast. With this release it seems like you fixed it (which is a great thing), but I couldn't find anything from the changelog that mentioned that something was done.

So I'm just asking if it was something that was fixed in particular, or was it for example a side effect of another glitch? Or I wonder if it only happened in Camel Duels...

We don't yet know the details, but I believe that rewriting some of mask checking functions in an earlier version caused problems in what must have been fragile and technically incorrect code of JJ2 at assembly level. The issue has been addressed in 5.0 and my modifications to the functions seemed to grant much more appropriate results (even better than in vanilla JJ2 or previous versions of JJ2+ for that matter).

(y)

Thanks, SE! Once we get another positive report (Jelly or Shaker) I'll replace the dll in the main zip with this one.

Why would you ever go for Windows 10 and expect anything to work on it.


As for the multiplayer announcements question, everybody settle down. We've been playing with these for many months now and barely even notice them, if anything finding them less obtrusive because they don't take up valuable space in the recent chat area that could have been used for seeing what actual players are saying. You've had them for less than 24 hours and have noticed that something is different than it was before. Give it a week or so and see how you feel.

I can also confirm that SE's dll works good on my Windows XP machine. Thanks for the quick fix!

Are there any new textured background options? I have ~20 waiting around; I can send them to be used in the next release.

Also, will there be new example levels? Any updates to the online version of plus-readme and plus-angelscript?

There are obviously a lot of readme changes. They're still at the same location:

http://www.jazz2online.com/jj2plus/p...gelscript.html
http://www.jazz2online.com/jj2plus/plus-readme.html

I'm not sure there's demand for more textured backgrounds to be included in the next release, but feel free to put them here and the dev team can see if any would be good to include.

Press F5 if you're not seeing any changes, it should work then.

I'm not sure if we're having a miscommunication here, but the release has already happened. It was yesterday.

Textures can be loaded from external files with jjSTREAM, transferred to a jjPIXELMAP, and then saved into the textured background from there, so strictly speaking if you have something you want people to be able to use it doesn't actually need to be in plus.j2d.

The angelscript one is still the old one... nothing too major, as the new readme i included with the download. Still, it'd be nice to get it online, too.

Or shift + f5/cmd+r if even that doesn't work.

Oops. Deleted cookies, works fine now. ;D

That wasn't my point. To play in fullscreen in Windows 8, there's a fix which disables Vsync and TrippleBuffer and in 60Hz monitors it sucks [Screen tearing, shaking] when playing with more FPS. So if it was possible to limit the FPS with plus.ini or something like that- the game would run atleast smoothly. Windows 10 is same as 8, that's why I said it.

I mean no you're right it was an unnecessarily flippant response. But that's interesting. Are you saying regular JJ2, which is limited to 70 FPS, runs properly with that fix applied?

EDIT: Sir Ementaler informs me that regular JJ2 may have been lying in that regard.

Solution: Dual boot Windows 7 or earlier and 10.

Or emulate.

Since its 70 FPS, its still a bit choppy but when I test both Plus and regular JJ2- I find the regular JJ2 runs comparatively smoother. So atleast do something to set FPS limit [Without Vsync game never gets smooth but atleast if its possible to make FPS limited to refresh rate; it becomes smooth enough].

Thats why I want an option to set the FPS limit.

Also, if its possible make the rendering mode to Direct 3D, then theres no need of FPS limit option as Windows 8/10 won't have issues with Fullscreen mode then.

@Robo: Its not solution at all. Why would I waste my HDD space with dual OS?

I call placebo.

@SE: Whats your monitors Refresh Rate?

Edit: Are you guys even have plans for putting option for FPS limit? Yes or no?

My screen's refresh rate is 60 Hz. I experience no tearing.

Here's behavior of JJ2 regarding fps, according to my experience with the code (BlurredD may negate it if I'm wrong):
- in fullscreen: JJ2 and JJ2+ limit fps to the screen's refresh rate (if obtainable).
- in windowed mode: JJ2 and JJ2+ have no known limits of fps, although both seem to be capped at around 140 most of the time. Unlike JJ2+, JJ2 lies and shows the frame rate as 70 if it's any higher than that.

I experience no tearing if only Fulscreen in OS below Windows 8.

In Fullscreen above Windows 7- FPS doesnt limit.
In Window in all OS- 135 FPS was max I got and most of the time it remains at 120.

Even if JJ2 lies, I found regular JJ2 more smoother than JJ2+.


Now, what about answer to my second question in my last post?

No. I don't know how or why, but for me on Windows 8 (with DDraw Hardware Accel disabled in Windows) vanilla JJ2 runs exceptionally smoother than Plus.

Monitor max refresh rate doesn't seem to affect it, as the result appears the same on both my 60hz and 75hz LCD screens. It's nowhere near unplayable tearing, in fact it's rather minimal. But it's definitely existent.

Plus appears to push my FPS all the way to around 120 in fullscreen (if it isn't lying), which is way too much and no doubt the cause of the tearing. Similar tearing happens with other games if FPS far exceeds the monitor refresh rate, even Direct3D/OpenGL rendered games.

For that I too suggest a manual FPS setting, if no Direct3D/OpenGL mode could be supported. I know it's easy for a non-techy like me to say all this, but it's just a suggestion that might enhance the JJ2 experience for future generations. 8D

I hear from some people that you guys broke cerebro

just wanted to point out that elec joined as cerebro still

k bye

No, Plus merely removes artificial limit of 70 from the FPS counter, not the actual FPS value itself.

Windows XP? Why the hell would you want Win XP in 2015?

My old PC still have Windows 98. Fortunately, it can't run JJ2 anymore [Long story, changed the hardwares to more low]. So if the question is "Why the hell would you wan't Win XP in 2015?" The answer is "If we can/or many people still uses Windows 95- why can't we use Windows XP?"

Also, Windows XP is the last OS where 320x240 was supported in Fullscreen if Vista doesn't support it [Never used Vista, so can't tell about it].
_____________
This is what I've trying to explain the whole time.

I know what you are trying to explain but you are wrong.
I said it once but I can say it again. In windowed mode your fps is uncapped in both JJ2 and JJ2+. Your JJ2 probably runs at about 300 fps and your JJ2+ probably runs at around 140, presumably because it executes reasonably more code per frame. JJ2+ displays fewer frames per second than JJ2 in windowed mode.
In fullscreen mode both JJ2 and JJ2+ try to adapt to your screen refresh rate or whatever else your system informs the game is the most optimal. Hence some people may see 60 fps and others may see 75 or 120 but it's capped and consistent between versions. JJ2+ displays the same number of frames per second as JJ2 in fullscreen mode.
To view your real frame rate in vanilla JJ2 (or nearly real, as still limited to 256 on display), use Cheat Engine to no-op the mov operation at 0043E447 in 1.23 or 0043E2FC in 1.24.
You experience tearing because you disabled triple buffering.
We will do nothing to fix bugs that don't exist.

Ok ok, sorry. I'll no more ask about FPS limit option. Btw, I know very well that in Fullscreen JJ2's FPS is capped to that of refresh rate.

Because Win7 lags the crap out of my old machine. What do you expect of a Celeron CPU, a Radeon 9200 and 1 GB RAM?

I know that feel.
For 10 years more exactly.

Believe me, if switching to Direct3D or whatever other technology were that easy, we'd have done it.

I second this. I totally agree. It's too distracting for serious play.

No. You are wrong. For me and much more players I asked, it's more important to see if there's a player on your screen you can hit, or if there is any pickup available than seeing if you roasted someone or someone lost the flag. Please make it custom so we can turn it off if we want to. It's easy to do. Please.

Also I noticed one bug. If you are playing Single Player, then use jjmorph to morph to frog or bird, and go to warp - you wont warp (just like before). But, if you then go away from the warp and use jjmorph again to morph to Jazz/Spaz/Lori, you will warp automatically, even tho you are not in the warp at that time.

I understand the sentiment, but besides the assertion that it is "easy to do" (which is never a wise thing to say about a software project you don't know the inner workings of), Violet never said anything to the contrary. He just asked everyone to give it a chance and see if you still think it's annoying after playing with it for a short while. Which I think is perfectly reasonable, as the first reaction to change is usually annoyance just because it's different, regardless of whether it's actually worse.

Which it could be! But let's see if maybe it's just the change everyone needs to adjust to. If a lot of people still think it's annoying after that, I'm sure the team will consider making changes.

Ok, sorry, I didn't expect anything to be fixed. I just expressed what I saw, and tried to determine what caused it without knowing Plus' technical details. The tearing is thus clearly a side effect caused by turning Hardware Accel off in Windows, and can't be helped by the Plus team anyway as it's not a Plus problem.

Nevertheless, on my Win8 setup, there is less tearing on Vanilla JJ2 than on Plus. Maybe it's a coincidence due to the lower framerate caused by Plus. I don't know or go into the technical reason, it just is, and it doesn't really matter either.

On a positive note, I'm really enjoying Plus' new features so far the past 2 days. The HUD messages, muts like weaponBunny, and even Lori's authentic gun are awesome! Really looking forward to the Bash now. ;)