pouët.net

Fully booked :(

ok, so won't attend :-(

Organizers: we might bring an Amiga demo,but we have well known lyrics in the music.Yeah,as in well known. Are we able to compete then or how do you see this? Last year Hoffman had to remove his well known lyrics from his tracked music entry,and I suspect that we might get hit by the same rules/laws/whatever?

Corial: sadly yes.

Corial : contact us thru mail please ;)

Franky: which one :) ?

Corial: hotline-2014@revision-party.net should work.

You've got mail,Franky & D.Fox

No problem, just let´s go to the Brathering instead!

@D.Fox Sent mail to the hotline but no answer at all... is it working?

Anyway, I think answering in the thread will be useful to others so:

My first question was about GEMA policies for this year. Will the GEMA policy continue as last year (so, no one at GEMA/BIEM is able to submit music to any compo)?

My second is about the Windows ecosystem for size-limited intros. Basically Windows version and the ability (or not) to compile shaders at runtime...

Thank you so much :)

merry: We received the mail. Please give us a bit more time to answer. Many of us want to celebrate new years and are on vacation.

GEMA just published a new pricing scheme in december and we don't have all the details on those yet to answer your question. But it is safe to assume that it'll even get more expensive next year, so our policies regarding GEMA/BIEM members will probably stay the same unless we find a very generous sponsor to pay for that.

The compo rules are being finalized currently - so you can expect an answer to your second question soon.

Thank you... I will stay tuned then!

I'm currently working on an 8k intro that depends on d3d11.dll and d3dcompile_47.dll and requires DirectX 11.0, so the target platform would be Windows 8.1. Could you please provide that for the intro PC?
I'll try to (additionally) offer backward-compatible binaries for earlier windows versions, if I have the time before the party, at most in a final version after release.

Small reminder:
And I still don´t want my car windows to be smashed in again....
Stichwort: Parkplatzüberwachung bei Nacht. Danke :)

Sir: we actually have a QM installed in Revision organizing... so it's on the list.

xtr1m : we havent made the OS version for the compo public yet, so untill then its all speculation :)

I wasn't asking to know what OS there will be, I was asking you to please provide Windows 8.1 :)

Well as said we havent decided on that yet :D

franky: he's trying to bribe you!

What was that stuff they had out before people were let in the hall ... ? Oh yeah! Hazelnut Vodka. Supposed to taste like candy or something. Send some of that. ;)

A bribe? Well, let me put it this way: You do want a lot of entries for your compos, do you? :D jk

In case of windows 8.1 compo machine the immediate next question will be if we can use dx11.1/2 features or it has to be able to run on nvidia..
I'm not sure what's in _47.dll that _43 (last dx enduser runtime) cannot do (albeit compiling slower), maybe apart from some dx11.1/2 features.
I imagine I will end up going back to the d3dx version for the final build, saving those bytes the _47/_43 dynamic loading takes ;)

You don't need to take care of dynamically loading _47 or _43, as far as I know there's already a crinkler command-line argument that allows you to route calls to another dll.

Sure, but then it's still dependent on one of them (meaning you would have to supply twice the number of exes). And less user friendly than trying to load one or the other, and still taking up a few more bytes than the d3dx version (but naturally way less than the dynamic dll loader).
But why would you need _47 except for compilation speed? (which may also be relevant by itself, especially if not compiling multithreaded)