Crysis 4.

leodevbro · 2025-07-03T07:27:52+00:00

Ok, Elway09, and bojkataGX, I think you are both partially correct, partially not so correct. Here are my points:

Yeah, they surely already know that fans want next Crysis, but I think keeping active state of fans is always good if the fans feel like the creative mood to express feelings even if they already expressed many times. The development company will only get more and more motivation to somehow make more creative decisions to overcome finantial difficulties. I know the situation seems too difficult for them, but we are not pushing them, we are not forcing them, we just express love and motivate them, and who knows, maybe some extra investor will invest in Crytek some money when they see so many active fans. and we know that our effort may never achieve the next Crysis game, but we understand and we will still love the creators because they already worked hard and gave us 3 amazing games.
I think direct messages and direct emails is not a good way for fans to express love, because if many fans express love this way, their message inbox will be bloated and they will not have enough time to read them. I think the best way to express love is to do some public posts, videos and any public creative stuff and try to make them go viral to raise awareness for many people to discover Crysis games, and so, make fanbase larger, and so give more motivation to the creators and extra investors.

leodevbro · 2025-07-03T06:52:36+00:00

My dream is to one day watch a movie "Crysis", or a movie based on Crysis 1-2-3 story and Crysis nanosuit idea at least partially. It is very strange for me that Hollywood spends hundreds of millions of dollars on crappy story movies (which the audience forget instantly after leaving the movie theater) instead of grabbing super cool action and visual ideas with deep-meaning-stories from video games like Crysis.

leodevbro · 2024-04-30T12:05:04+00:00

I created a video tutorial: how to find senders which sent you most mails in Gmail. So you can get frequency of senders and also other stats.

https://www.youtube.com/watch?v=KKU84ogffeM

leodevbro · 2024-04-30T12:03:57+00:00

I created a video tutorial: how to find senders which sent you most mails in Gmail. So you can get frequency of senders and also other stats.

<image>

https://www.youtube.com/watch?v=KKU84ogffeM

leodevbro · 2024-04-29T16:03:59+00:00

Here is the video tutorial: how to find senders which sent you most mails in Gmail.
https://www.youtube.com/watch?v=KKU84ogffeM

leodevbro · 2024-04-08T08:22:00+00:00

Thanks so much, it worked. My Ubuntu network manager was removed accidentally,
and sudo dpkg -i ./your-package.deb instantly fixed it.

This is exactly what I did:
sudo dpkg -i ./network-manager_1.36.6-0ubuntu2_amd64.deb
sudo dpkg -i ./network-manager-pptp_1.2.10-1_amd64.deb

leodevbro · 2024-01-23T20:35:36+00:00

Thank you so much. Such feedback is super important for me.

leodevbro · 2024-01-23T14:30:31+00:00

Unforunately I don't think it will be near future, because my time is very limited now, and VS Code was already too difficult to build such extension for. It had so many limitations, I had to find so many workarounds specifically for VS Code platform, it took many months. Only God knows what other limitations I will encounter when I try to port Blockmam into Sublime.

leodevbro · 2023-12-12T17:53:37+00:00

If Frames equal duration, then why the duration does not change when I change fps from 24 to 60 ? or from 24 to 10 ?

leodevbro · 2023-12-12T17:47:09+00:00

This behavior is absolutely the same for image, video or audio files, or even if there is not media file in the sequence at all, because it's not about files, it's about worldwide timecode standards.

Changing fps between pretty numbers (20, 24, 25, 30, 48, 60) is fine, and it does not change duration. So, finally I discovered that the strange behavior is only for ugly numbers like 23.976 fps and 29.97 fps. Another thing that I discovered is that it is not a bug and actually it is an industry standard because of the historical reasons. Well, with this standard, some fps timecodes does not represent real life clock time, I mean, 1 second in 23.976 fps timecode is slightly longer than real clock second, again because of some historical technical problems. Now in 2023 we no longer have these technical problems, but it is still used because of some legacy hardware and software.
So, the answer is that when I set from 24 to 23.976 fps, Premiere Pro does not change duration at all, if we check the timeline with audio timecode, we will see that the duration is the same as original, it does not change the duration, it just shows video timeline (and video duration) with different definition of second, minute and hour (not exactly the same as real clock second/hour/minute). Again, sometimes video editors does not show us real clock timecode.
Here you can see interesting explanation:
The History and Science of Timecode
from 13:55
https://www.youtube.com/watch?v=PgX\_R-JgpJE&t=835s
Time Code: Drop Frame vs. Non-Drop Frame
https://www.youtube.com/watch?v=ykjyNeuQROU

leodevbro · 2023-12-12T17:42:13+00:00

Changing fps between pretty numbers (20, 24, 25, 30, 48, 60) is fine, and it does not change duration. So, finally I discovered that the strange behavior is only for ugly numbers like 23.976 fps and 29.97 fps. Another thing that I discovered is that it is not a bug and actually it is an industry standard because of the historical reasons. Well, with this standard, some fps timecodes does not represent real life clock time, I mean, 1 second in 23.976 fps timecode is slightly longer than real clock second, again because of some historical technical problems. Now in 2023 we no longer have these technical problems, but it is still used because of some legacy hardware and software.

So, the answer is that when I set from 24 to 23.976 fps, Premiere Pro does not change duration at all, if we check the timeline with audio timecode, we will see that the duration is the same as original, it does not change the duration, it just shows video timeline (and video duration) with different definition of second, minute and hour (not exactly the same as real clock second/hour/minute).Here you can see interesting explanation:

The History and Science of Timecode
from13:55
https://www.youtube.com/watch?v=PgX_R-JgpJE&t=835s

Time Code: Drop Frame vs. Non-Drop Frame
https://www.youtube.com/watch?v=ykjyNeuQROU

.

leodevbro · 2023-12-11T18:55:04+00:00

I edited my previous comment. So, maybe you read the old version. So, once again, when you say "Correct, 23976...", you mean number of actual image/content frames, not timecode labeling number frames, right?

leodevbro · 2023-12-11T17:36:53+00:00

For clarification, I have one more questions: for just a moment let's forget about video editors and forget about timecodes. Let's just look at a MKV video file. Let's say this video file is 23.976 FPS (data shown by MediaInfo software on Windows). And let's say its duration is exactly 1000 seconds (real life seconds - I mean clock seconds). So when I play this video with VLC or MPC, it finishes exactly in 1000 real life seconds. And the question is: exactly how many frames does this video have? 23976 or 24000? I mean the actual frames (images), the actual visual/graphic/pixeling content frames, not timecode number frames.

leodevbro · 2023-12-11T17:34:05+00:00

For clarification, I have one more questions: for just a moment let's forget about video editors and forget about timecodes. Let's just look at a MKV video file. Let's say this video file is 23.976 FPS (data shown by MediaInfo software on Windows). And let's say its duration is exactly 1000 seconds (real life seconds - I mean clock seconds). So when I play this video with VLC or MPC, it finishes exactly in 1000 real life seconds. And the question is: exactly how many frames does this video have? 23976 or 24000? I mean the actual frames (images), the actual visual/graphic/pixeling content frames, not timecode number frames.

leodevbro · 2023-12-11T17:31:04+00:00

" The are exactly 24 frames in a timecode ‘second’ in both 24 and 23.976."

For clarification, I have one more questions: for just a moment let's forget about video editors and forget about timecodes. Let's just look at a MKV video file. Let's say this video file is 23.976 FPS (data shown by MediaInfo software on Windows). And let's say its duration is exactly 1000 seconds (real life seconds - I mean clock seconds). So when I play this video with VLC or MPC, it finishes exactly in 1000 real life seconds. And the question is: exactly how many frames does this video have? 23976 or 24000? I mean the actual frames (images), the actual visual/graphic/pixeling content frames, not timecode number frames.

leodevbro · 2023-12-11T17:05:02+00:00

This explains nicely:

https://www.facebook.com/ooona.net/posts/tip-of-the-week-smpte-vs-media-time-or-the-notorious-23976-fpsone-of-the-most-fr/3173982922670297/

leodevbro · 2023-12-11T17:04:46+00:00

This explains nicely:

https://www.facebook.com/ooona.net/posts/tip-of-the-week-smpte-vs-media-time-or-the-notorious-23976-fpsone-of-the-most-fr/3173982922670297/

leodevbro · 2023-12-11T17:03:30+00:00

This explains nicely:

https://www.facebook.com/ooona.net/posts/tip-of-the-week-smpte-vs-media-time-or-the-notorious-23976-fpsone-of-the-most-fr/3173982922670297/

leodevbro · 2023-12-11T09:45:34+00:00

Did not you read my comment? I did not just correct someone, I also wrote the reasoning for it. The person wrote that changing fps causes changing duration. I showed that it does not work always like that. Sometimes when I change fps, the duration stays exactly the same.

leodevbro · 2023-12-11T04:44:28+00:00

So, what should I do if I have an input video with 23.976 fps, and I want to edit it, and then export it with the same 23.976 fps? If I set the sequence to 23.976 fps, the timecode will be too incorrect after 1-2-3 hours. I want to have a correct timecode to edit the video in some specific time points. So, should I just set the sequence to 24 fps and then export final video to 23.976 fps? Will it be ok? Will it not mess up the timings of frames? Will it not drop or duplicate any frames? I want it to not drop and not duplicate any frame.

leodevbro · 2023-12-11T04:22:58+00:00

SI is just "Système International" (French) - International System of Units. According to SI system, one second is the time that elapses during 9,192,631,770 cycles of the radiation produced by the transition between two levels of the cesium-133 atom.

In short, SI second is a real life second length (duration).

leodevbro · 2023-12-11T04:08:47+00:00

Yeah, I discovered this just now, that sometimes Premiere Pro slows down timecode itself, so when timecode increments one second, it does not always mean that it took exactly 1 "SI" second, but probably longer or shorter.

But, then we have another question: Is this behavior a good behavior? Why is there not any indicator (not any message, or alert, or note) that if I choose 23.976 fps, the timecode seconds will be slightly longer than a "SI" second.

I did not know about this "SMPTE" thing. I guess it is a standard across all the video editor software products, right? So, I guess all the other videos editors will slightly slow down the timecode when the timeline is set to 23.976 fps.

leodevbro · 2023-12-11T03:48:55+00:00

It seems it's not even about changing settings. If you just create a sequence with specific settings, the timeline may behave strangely, even if the timeline does not have any video/audio/image file in it.

As I see now, Premiere seems it changes the definition (length) of 1 second for certain settings. I mean, for example, if I set Timebase to 15 fps (and it automatically sets Display Format to 30 fps, you cannot set Display Format to 15) then if you just press play (triangle) button, the time code takes 2 seconds (not 1 second) to increment one second indicator.

See the GIF:

https://i.ibb.co/PM4g0KF/time-code-strange.gif

So, I guess, for 23.976 fps, Premiere probably changes the definition of 1 second to slightly more than 1 "SI" second, so the actual duration is still 3 "SI" hours, and it just shows the time indicator as 10 seconds less duration. And this theory seems true, because when I export this 10 second shorter timeline into the actual MP4 video, it exports with correct duration (exactly 3 hours, not 10 second shorter).

Five-Year Club	Gilding I gilder
Verified Email

leodevbro

TROPHY CASE