Question regarding making a "CSQC-game"

[Urre]

[Spike]

- What's the minimum SVQC I need to do in order to create a singleplayer game entirely in CSQC?

You need a compatible progs. All it needs to do is sit there and do nothing, basically. System functions need to be stubs. You probably want to stub the spawn functions too. Just empty functions.

- Can CSQC read map objects and spawn them like SVQC?

FTE yes, DP no.
The csprogs does the parsing itself.

- Does PVS work the same in CSQC?

Not entirely sure in what regard.
PVS is technically an optimisation rather than a specific feature.
Only pvs-visible ents are sent to clients, unless its set to send all ents. So yes, you can get ents removed and readded as the player moves around.
inside the csprogs, pvs is invisible to the csprogs. The engine just doesn't draw stuff that cannot be visible.

- What about savegames?

csqc doesn't save games.
The data needs to be fully replicatable. Stats and visible ents. Newly visible ents can have specific flags to send stuff if needed.

- Am I missing some important points regarding making a singleplayer game using as little SVQC and as much CSQC as possible?

You will need to implement movetypes yourself. Other than that, there's no reason that you cannot.
You cannot save the game in csqc unless you make your own save game function, or if you replicate the data to the server to. You can make your own save function though.

[Urre]

What about reading input for movement? How crazy complicated is it? I'm guessing this is kind of tying in with clientside prediction of movement

I actually meant pvs like monsters seeing you or not, gameplay related stuff basicly.

Bmodels are collideable and can push stuff?

[Spike]

- What about reading input for movement? How crazy complicated is it? I'm guessing this is kind of tying in with clientside prediction of movement :P

Prediction works thusly: The client generates input frames in a list. Its a ring buffer, basically. You grab the frames from 'acknowledged' to 'current' and apply those input packets to the state of the player. The result is your predicted player.
In a server-less environment you can use the same builtin, but go from 'last frame' to 'current', then save off current as last frame so as to avoid duplicates. (normally acknowleged increases in jumps or so).


- I actually meant pvs like monsters seeing you or not, gameplay related stuff basicly.

There's an fte extension builtin which will give a quick pvs success/fail result if really needed. Its not specifically csqc.
monster's sight is traditionally implemented using tracelines, not pvs.

- Bmodels are collideable and can push stuff?

bmodels are solid, but in the base csqc spec they do not push (this is because there is no .movetype support in the base csqc spec - and thus no think/nextthink either, although that's not always an issue - it was meant to be a followup extension as the engine needs a lot of code, and I wanted a spec that was remotely plausable without rewriting the entire engine from scratch straight off).

[LordHavoc]

[Spike]

movetype_push has slightly different nextthink semantics from other movetypes. and without movetypes, those semantics cannot be fully honoured, hence no thinks.
but yeah, you can emulate it in predraw just fine, even if its never drawn, so I never saw this as a major issue.
DP supporting it might be, but mneh, better to get on with full movetypes support.

[Urre]

Checking pvs before doing a traceline can be a useful optimization, just saying.

But yes, I'm not entirely sure how to interpret the pusher-stuff. Can I or can I not have doors and lifts? Is it done somehow different from SSQC?

DP really should add the ability to load mapobjects.

[LordHavoc]

[Spike]

[LordHavoc]

[LordHavoc]

[Urre]

[Spike]

[LordHavoc]

[Urre]

Looks very, very interesting, although it seems to me like the rotational pushing is either incomplete or I'm missing something? I'm having trouble following how pushstartforward and those actually work, and am suspecting those do the magic, really. You say they're not being set, and I don't really see how they'd be set, making this code hard for me to base anything on. Otherwise awesome stuff!