Public access to development versions

[datiswous]

Mabe better to not clutter this thread with feature requests and discussion about that? Just keep this about dev-testing.

[lowenz]

"Added r_fboScaling cvar which allows to change Render scale filtering to nearest."

It works really well, performance on par with setting the equivalent resolution in the same scene (1280x120 vs 2560x1440 with 0.5 scaling and nearest filtering) without needing to force the integer upscaling in the drivers (sharper image than bilinear/bicubic for who prefers the blocky look)

Edited April 21 by lowenz

[stgatilov]

6 hours ago, thebigh said:

WARNING:LibJPEG: JPEG parameter struct mismatch: library thinks size is 584, caller expects 568
Segmentation fault (core dumped)

Yes, @nbohr1more has them too.

Quote

My libjpeg-dev version is the latest available, 8c-2ubuntu8.

TDM does not use system libraries so your version should not matter.

Quote

I did not have this problem in dev16481-9881.

That's very strange: the changes in libjpeg first appeared in dev16481-9881, so the same problem should happen on that build too.

[AluminumHaste]

5 hours ago, lowenz said:

Well, zink is ready to use nowdays

From Mesa 22.1 on Windows too.

 

Quote

we are not a conformant OpenGL implementation

 

 

That doesn't inspire confidence.

[stgatilov]

21 hours ago, thebigh said:

I'm now getting errors looking like this when I try to save a game:

WARNING:LibJPEG: JPEG parameter struct mismatch: library thinks size is 584, caller expects 568
Segmentation fault (core dumped)

The save game itself gets written and loads without issue, but it has no preview thumbnail.

Fixed libjpeg in trunk.

You might want to change r_screenshot_format to avoid using jpeg for savegame screenshots.
Although it won't help you if someone uses jpeg file in texture or as SEED map.

[datiswous]

4 hours ago, stgatilov said:

Although it won't help you if someone uses jpeg file in texture or as SEED map.

Is this not only an issue with writing jpgs? Texture is loading if I'm correct.

Edited April 22 by datiswous

[Araneidae]

Hmmmm.  Just switched to the latest beta dev16485-9903 (from the previous one, dev16481-9881 ) and restarted the mission I was playing (Iris ... what an amazing mission, very happy to start from the top again, even though I'm only halfway through!), first thing I do is create a save game ... and bang! down it goes.

Nothing in the console log:

Changed location from '' to 'location_home'.
Switching to EFX 'location_home' (#15)
The ambient 'snd_home' (solitude_loop_z) for location 'location_home' is now playing.
The ambient 'snd_home' (solitude_loop_z) for location 'location_home' is now playing.
WARNING:LibJPEG: JPEG parameter struct mismatch: library thinks size is 584, caller expects 568
Segmentation fault (core dumped)

There was a very long pause before it crashed.

Will try again ... well, that was interesting, looks as if the saved game was good.  However, played for a little, hit F4 and ... hangs and crashes again, messages as before.  That's a shame.

Ah!  Looks like the conversation above covers this very issue.  Will go back to the previous beta for now.

Edit: Yes, can confirm that -9881 works and -9903 crashes when saving the game.

Edited April 23 by Araneidae
Got versions the wrong way around!

[datiswous]

I had a similar crash in 2.10 with the save room saving in Hazard Pay. But maybe it is unrelated.

[datiswous]

On 4/23/2022 at 3:34 PM, Araneidae said:

There was a very long pause before it crashed.

I have the same. It also happens when making a screenshot.

[datiswous]

On 3/7/2022 at 1:01 PM, stgatilov said:

JPEG saving and loading crashes on Linux. Setting r_screenshot_format to "png" may help...

It works for creating screenshots. Saving still crashes to desktop.

[stgatilov]

dev16487-9919 is public.

At the very least, the Linux crash should be fixed there.

[lowenz]

Just reporting: OpenAL Soft has been updated to 1.22

[lowenz]

With now full EAX support, and XRAM emulation too!

From the log of UT3 (I use it as a benchmark)

 

Init: ALAudio device requested : 
Init: ALAudio device opened    : OpenAL Soft
Init: AL_VENDOR      : OpenAL Community
Init: AL_RENDERER    : OpenAL Soft
Init: AL_VERSION     : 1.1 ALSOFT 1.22.0
Init: AL_EXTENSIONS  : EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX-RAM AL_EXT_ALAW AL_EXT_BFORMAT AL_EXT_DOUBLE AL_EXT_EXPONENT_DISTANCE AL_EXT_FLOAT32 AL_EXT_IMA4 AL_EXT_LINEAR_DISTANCE AL_EXT_MCFORMATS AL_EXT_MULAW AL_EXT_MULAW_BFORMAT AL_EXT_MULAW_MCFORMATS AL_EXT_OFFSET AL_EXT_source_distance_model AL_EXT_SOURCE_RADIUS AL_EXT_STEREO_ANGLES AL_LOKI_quadriphonic AL_SOFT_bformat_ex AL_SOFTX_bformat_hoa AL_SOFT_block_alignment AL_SOFT_callback_buffer AL_SOFTX_convolution_reverb AL_SOFT_deferred_updates AL_SOFT_direct_channels AL_SOFT_direct_channels_remix AL_SOFT_effect_target AL_SOFT_events AL_SOFT_gain_clamp_ex AL_SOFTX_hold_on_disconnect AL_SOFT_loop_points AL_SOFTX_map_buffer AL_SOFT_MSADPCM AL_SOFT_source_latency AL_SOFT_source_length AL_SOFT_source_resampler AL_SOFT_source_spatialize AL_SOFT_UHJ
Init: Device supports: EAX4.0
Init: Device supports: EAX-RAM
Init: Device supports: ALC_EXT_EFX
Init: Found EFX extension with 8 effect slots and 5 potential sends
Init: ...'reverb' supported
Init: ...'equalizer' supported
Init: ...'low pass filter' supported
Init: XRAM           : YES
Init: ALAudioDevice initialized.
Init: Client initialized

Edited May 5 by lowenz

[Angelot]

Is the latest version (2.10) backwards compatible with older missions?

[MirceaKitsune]

4 hours ago, Angelot said:

Is the latest version (2.10) backwards compatible with older missions?

If it wasn't I imagine panic would ensue, as this would be equivalent to starting from scratch and most FM's would be lost forever only playable on archived versions of TDM.

[Angelot]

1 hour ago, MirceaKitsune said:

If it wasn't I imagine panic would ensue, as this would be equivalent to starting from scratch and most FM's would be lost forever only playable on archived versions of TDM.

Ok, thanks.

Edited May 7 by Angelot

[Gadavre]

Very serious problem with the launch of the new version (dev16487-9919) on windows 7.

Edited May 29 by Gadavre

[stgatilov]

17 hours ago, Gadavre said:

Very serious problem with the launch of the new version (dev16487-9919) on windows 7.

It applies to all dev builds I think.
I have added it to changelog as "known problem".

For more detail, go here:

 

[stgatilov]

dev16498-9944 is now public!

P.S. This is how I celebrate resurrection of my PC

[AluminumHaste]

Congrats on PC Jesus

[stgatilov]

dev16519-9985 is now public.

[stgatilov]

dev16574-10036 is now public.

This includes tons of assets fixes, GUI warnings, and BVH-assisted optimizations.
Quite a lot of breakage potential

[madtaffer]

1 hour ago, stgatilov said:

dev16574-10036 is now public.

This includes tons of assets fixes, GUI warnings, and BVH-assisted optimizations.
Quite a lot of breakage potential

How long till beta?

[AluminumHaste]

15 hours ago, madtaffer said:

How long till beta?

When the Vulkan renderer is ready

 

 

 

 

 

 

 

 

 

 

 

 

 

[Araneidae]

Please can we have some attention to the current disconnect between the stealth score and the guard alert level and discovery status for the new release?